This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

TCP timestamps

The following is reported as a Medium Vulnerabiity on my ASG 9.003 (Latest) via Security Space Advanced Security Audit

How can I fix it?

Note: I did not make changes to my configuration, I do my scanning regularly, these are new vulnerabilities.

General: TCP timestamps
Description
general/tcp

Synopsis :

The remote service implements TCP timestamps.

Description :

The remote host implements TCP timestamps, as defined by RFC1323.
A side effect of this feature is that the uptime of the remote 
host can sometimes be computed.

See also :

http://www.ietf.org/rfc/rfc1323.txt


Synopsis :

The remote service implements TCP timestamps.

Description :

The remote host implements TCP timestamps, as defined by RFC1323.
A side effect of this feature is that the uptime of the remote 
host can sometimes be computed.

See also :

http://www.ietf.org/rfc/rfc1323.txt

WorkSheet Notes


This thread was automatically locked due to age.
  • Alvin, what possible use would it be to an attacker to know how long my Astaro has been up?  I don't see how/why this is anything that should be fixed, but I'm willing to learn.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
    • IIRC, Ambiron/TrustWave reports this as LOW or 'Informational', not 'Medium'.

      I also don't see any reason for this to be serious.

      Barry
      • Yes it's a real problem because :

        The most likely impact of this is that an attacker could try to determine the host’s patch status as certain updates require a reboot.

        So what is the solution to fix this please ?