<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic HP ILO 1.93 (and older)  Predictable TCP Initial Sequence Numbers Vulnerability in Server Management - Remote Server Management</title>
    <link>https://community.hpe.com/t5/server-management-remote-server/hp-ilo-1-93-and-older-predictable-tcp-initial-sequence-numbers/m-p/4336664#M4063</link>
    <description>Qualys security scanner reports HP ILO 1 ips as vulnerable to "Predictable TCP Initial Sequence Numbers Vulnerability", which breaks PCI DSS compliance ( &lt;A href="https://www.pcisecuritystandards.org/security_standards/pci_pa_dss.shtml" target="_blank"&gt;https://www.pcisecuritystandards.org/security_standards/pci_pa_dss.shtml&lt;/A&gt; ) according to Qualys.&lt;BR /&gt;&lt;BR /&gt;The impact is, that servers with HP ILO 1 can not be used in Payment Card Industry DSS compliant environments. Can someone report this as a bug?&lt;BR /&gt;&lt;BR /&gt;more information:&lt;BR /&gt;--&lt;BR /&gt;                     2    Predictable TCP Initial Sequence Numbers Vulnerability&lt;BR /&gt;             QID:                            82005                                                                   CVSS Base:               7.5               PCI FAILED&lt;BR /&gt;             Category:                       TCP/IP                                                                  CVSS Temporal:           5.4&lt;BR /&gt;             CVE ID:                         CVE-1999-0077, CVE-2000-0328, CVE-2000-0916, CVE-2001-0328&lt;BR /&gt;             Vendor Reference:               -&lt;BR /&gt;             Bugtraq ID:                     2682&lt;BR /&gt;             Modified:                       06/06/2008&lt;BR /&gt;             Edited:                         No&lt;BR /&gt;             THREAT:&lt;BR /&gt;             This server uses TCP/IP implementation that respects the "64K rule", or a "time dependent rule" for generating TCP sequence numbers. Unauthorized users can&lt;BR /&gt;             predict sequence numbers when two hosts are communicating, and connect to your server from any source IP address. The only difference with a legitimate&lt;BR /&gt;             connection is that the attacker will not see the replies sent back to the authorized user whose IP was forged.&lt;BR /&gt;             IMPACT:&lt;BR /&gt;             Some services, such as rsh or rlogin, may base their authentication on the source IP address. Since malicious users can forge the IP address of a trusted host, they&lt;BR /&gt;             can bypass authentication protocol. This problem may pose severe threats to any server offering Berkeley "r" services (rlogin, rsh, etc.) or any source IP-based&lt;BR /&gt;             authentication.&lt;BR /&gt;             If you do not provide such services, this problem is not critical. If you do use this kind of authentication protocol, unauthorized remote users can execute&lt;BR /&gt;             commands, and completely compromise your system. Therefore, this vulnerability can be considered dangerous and critical.&lt;BR /&gt;             SOLUTION:&lt;BR /&gt;             You may need to upgrade your Operating System to change the behavior of your TCP/IP stack regarding this problem.&lt;BR /&gt;             This cert advisory describes how to fix this issue : CA-2001-09 (&lt;A href="http://www.cert.org/advisories/CA-2001-09.html)" target="_blank"&gt;http://www.cert.org/advisories/CA-2001-09.html)&lt;/A&gt;&lt;BR /&gt;             For Microsoft systems you can apply this patch : MS99-046 (&lt;A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q243835&amp;amp;sd=tech):" target="_blank"&gt;http://support.microsoft.com/default.aspx?scid=kb;en-us;Q243835&amp;amp;sd=tech):&lt;/A&gt; How to Prevent&lt;BR /&gt;             Predictable TCP/IP Initial Sequence Numbers&lt;BR /&gt;             For Cisco IOS systems you can apply this patch : cisco-sa-20010301-ios-tcp-isn-random&lt;BR /&gt;             (&lt;A href="http://www.cisco.com/warp/public/707/cisco-sa-20010301-ios-tcp-isn-random.shtml):" target="_blank"&gt;http://www.cisco.com/warp/public/707/cisco-sa-20010301-ios-tcp-isn-random.shtml):&lt;/A&gt; Cisco IOS Software TCP Initial Sequence Number Randomization&lt;BR /&gt;             Improvements&lt;BR /&gt;             COMPLIANCE:&lt;BR /&gt;             Not Applicable&lt;BR /&gt;             RESULTS:&lt;BR /&gt;             Constant changes in initial sequence numbers observed in 22 out of 23 events.&lt;BR /&gt;             [ Sent Packets Results ]&lt;BR /&gt;             Packet 1 : TIME[1231344785.981295] SEQ[15149442] CHANGE[N/A] VARIATION[N/A]&lt;BR /&gt;             Packet 2 : TIME[1231344785.988236] SEQ[15149449] CHANGE[7] VARIATION[N/A]&lt;BR /&gt;             Packet 3 : TIME[1231344785.995231] SEQ[15149456] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 4 : TIME[1231344786. 2236] SEQ[15149463] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 5 : TIME[1231344786. 9229] SEQ[15149470] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 6 : TIME[1231344786. 16228] SEQ[15149477] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 7 : TIME[1231344786. 23225] SEQ[15149484] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 8 : TIME[1231344786. 30224] SEQ[15149491] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 9 : TIME[1231344786. 37224] SEQ[15149498] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 10 : TIME[1231344786. 44222] SEQ[15149505] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 11 : TIME[1231344786. 51222] SEQ[15149512] CHANGE[7] VARIATION[0]&lt;BR /&gt;Payment Card Industry (PCI) Technical Report                                                                                                                                 page 200&lt;BR /&gt;Packet 12 : TIME[1231344786. 58220] SEQ[15149519] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 13 : TIME[1231344786. 65220] SEQ[15149526] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 14 : TIME[1231344786. 72219] SEQ[15149533] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 15 : TIME[1231344786. 79218] SEQ[15149540] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 16 : TIME[1231344786. 86216] SEQ[15149547] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 17 : TIME[1231344786. 93216] SEQ[15149554] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 18 : TIME[1231344786.100217] SEQ[15149561] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 19 : TIME[1231344786.107218] SEQ[15149568] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 20 : TIME[1231344786.114213] SEQ[15149575] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 21 : TIME[1231344786.121212] SEQ[15149582] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 22 : TIME[1231344786.128210] SEQ[15149589] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 23 : TIME[1231344786.135210] SEQ[15149596] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 24 : TIME[1231344786.142208] SEQ[15149603] CHANGE[7] VARIATION[0]&lt;BR /&gt;Constant changes in initial sequence numbers observed in 21 out o&lt;BR /&gt;f 23 events.&lt;BR /&gt;Packet 1 : TIME[1231344839.390171] SEQ[15202848] CHANGE[N/A] VARIATION[N/A]&lt;BR /&gt;Packet 2 : TIME[1231344839.398113] SEQ[15202856] CHANGE[8] VARIATION[N/A]&lt;BR /&gt;Packet 3 : TIME[1231344839.405109] SEQ[15202863] CHANGE[7] VARIATION[1]&lt;BR /&gt;Packet 4 : TIME[1231344839.412108] SEQ[15202870] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 5 : TIME[1231344839.419107] SEQ[15202877] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 6 : TIME[1231344839.426107] SEQ[15202884] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 7 : TIME[1231344839.433106] SEQ[15202891] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 8 : TIME[1231344839.440104] SEQ[15202898] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 9 : TIME[1231344839.447107] SEQ[15202905] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 10 : TIME[1231344839.454102] SEQ[15202912] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 11 : TIME[1231344839.461101] SEQ[15202919] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 12 : TIME[1231344839.468111] SEQ[15202926] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 13 : TIME[1231344839.475101] SEQ[15202933] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 14 : TIME[1231344839.482098] SEQ[15202940] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 15 : TIME[1231344839.489096] SEQ[15202947] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 16 : TIME[1231344839.496095] SEQ[15202954] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 17 : TIME[1231344839.503094] SEQ[15202961] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 18 : TIME[1231344839.510093] SEQ[15202968] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 19 : TIME[1231344839.517100] SEQ[15202975] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 20 : TIME[1231344839.524091] SEQ[15202982] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 21 : TIME[1231344839.531089] SEQ[15202989] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 22 : TIME[1231344839.538089] SEQ[15202996] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 23 : TIME[1231344839.545088] SEQ[15203003] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 24 : TIME[1231344839.552088] SEQ[15203010] CHANGE[7] VARIATION[0]&lt;BR /&gt;</description>
    <pubDate>Tue, 13 Jan 2009 13:09:27 GMT</pubDate>
    <dc:creator>askotamm</dc:creator>
    <dc:date>2009-01-13T13:09:27Z</dc:date>
    <item>
      <title>HP ILO 1.93 (and older)  Predictable TCP Initial Sequence Numbers Vulnerability</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/hp-ilo-1-93-and-older-predictable-tcp-initial-sequence-numbers/m-p/4336664#M4063</link>
      <description>Qualys security scanner reports HP ILO 1 ips as vulnerable to "Predictable TCP Initial Sequence Numbers Vulnerability", which breaks PCI DSS compliance ( &lt;A href="https://www.pcisecuritystandards.org/security_standards/pci_pa_dss.shtml" target="_blank"&gt;https://www.pcisecuritystandards.org/security_standards/pci_pa_dss.shtml&lt;/A&gt; ) according to Qualys.&lt;BR /&gt;&lt;BR /&gt;The impact is, that servers with HP ILO 1 can not be used in Payment Card Industry DSS compliant environments. Can someone report this as a bug?&lt;BR /&gt;&lt;BR /&gt;more information:&lt;BR /&gt;--&lt;BR /&gt;                     2    Predictable TCP Initial Sequence Numbers Vulnerability&lt;BR /&gt;             QID:                            82005                                                                   CVSS Base:               7.5               PCI FAILED&lt;BR /&gt;             Category:                       TCP/IP                                                                  CVSS Temporal:           5.4&lt;BR /&gt;             CVE ID:                         CVE-1999-0077, CVE-2000-0328, CVE-2000-0916, CVE-2001-0328&lt;BR /&gt;             Vendor Reference:               -&lt;BR /&gt;             Bugtraq ID:                     2682&lt;BR /&gt;             Modified:                       06/06/2008&lt;BR /&gt;             Edited:                         No&lt;BR /&gt;             THREAT:&lt;BR /&gt;             This server uses TCP/IP implementation that respects the "64K rule", or a "time dependent rule" for generating TCP sequence numbers. Unauthorized users can&lt;BR /&gt;             predict sequence numbers when two hosts are communicating, and connect to your server from any source IP address. The only difference with a legitimate&lt;BR /&gt;             connection is that the attacker will not see the replies sent back to the authorized user whose IP was forged.&lt;BR /&gt;             IMPACT:&lt;BR /&gt;             Some services, such as rsh or rlogin, may base their authentication on the source IP address. Since malicious users can forge the IP address of a trusted host, they&lt;BR /&gt;             can bypass authentication protocol. This problem may pose severe threats to any server offering Berkeley "r" services (rlogin, rsh, etc.) or any source IP-based&lt;BR /&gt;             authentication.&lt;BR /&gt;             If you do not provide such services, this problem is not critical. If you do use this kind of authentication protocol, unauthorized remote users can execute&lt;BR /&gt;             commands, and completely compromise your system. Therefore, this vulnerability can be considered dangerous and critical.&lt;BR /&gt;             SOLUTION:&lt;BR /&gt;             You may need to upgrade your Operating System to change the behavior of your TCP/IP stack regarding this problem.&lt;BR /&gt;             This cert advisory describes how to fix this issue : CA-2001-09 (&lt;A href="http://www.cert.org/advisories/CA-2001-09.html)" target="_blank"&gt;http://www.cert.org/advisories/CA-2001-09.html)&lt;/A&gt;&lt;BR /&gt;             For Microsoft systems you can apply this patch : MS99-046 (&lt;A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q243835&amp;amp;sd=tech):" target="_blank"&gt;http://support.microsoft.com/default.aspx?scid=kb;en-us;Q243835&amp;amp;sd=tech):&lt;/A&gt; How to Prevent&lt;BR /&gt;             Predictable TCP/IP Initial Sequence Numbers&lt;BR /&gt;             For Cisco IOS systems you can apply this patch : cisco-sa-20010301-ios-tcp-isn-random&lt;BR /&gt;             (&lt;A href="http://www.cisco.com/warp/public/707/cisco-sa-20010301-ios-tcp-isn-random.shtml):" target="_blank"&gt;http://www.cisco.com/warp/public/707/cisco-sa-20010301-ios-tcp-isn-random.shtml):&lt;/A&gt; Cisco IOS Software TCP Initial Sequence Number Randomization&lt;BR /&gt;             Improvements&lt;BR /&gt;             COMPLIANCE:&lt;BR /&gt;             Not Applicable&lt;BR /&gt;             RESULTS:&lt;BR /&gt;             Constant changes in initial sequence numbers observed in 22 out of 23 events.&lt;BR /&gt;             [ Sent Packets Results ]&lt;BR /&gt;             Packet 1 : TIME[1231344785.981295] SEQ[15149442] CHANGE[N/A] VARIATION[N/A]&lt;BR /&gt;             Packet 2 : TIME[1231344785.988236] SEQ[15149449] CHANGE[7] VARIATION[N/A]&lt;BR /&gt;             Packet 3 : TIME[1231344785.995231] SEQ[15149456] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 4 : TIME[1231344786. 2236] SEQ[15149463] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 5 : TIME[1231344786. 9229] SEQ[15149470] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 6 : TIME[1231344786. 16228] SEQ[15149477] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 7 : TIME[1231344786. 23225] SEQ[15149484] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 8 : TIME[1231344786. 30224] SEQ[15149491] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 9 : TIME[1231344786. 37224] SEQ[15149498] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 10 : TIME[1231344786. 44222] SEQ[15149505] CHANGE[7] VARIATION[0]&lt;BR /&gt;             Packet 11 : TIME[1231344786. 51222] SEQ[15149512] CHANGE[7] VARIATION[0]&lt;BR /&gt;Payment Card Industry (PCI) Technical Report                                                                                                                                 page 200&lt;BR /&gt;Packet 12 : TIME[1231344786. 58220] SEQ[15149519] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 13 : TIME[1231344786. 65220] SEQ[15149526] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 14 : TIME[1231344786. 72219] SEQ[15149533] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 15 : TIME[1231344786. 79218] SEQ[15149540] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 16 : TIME[1231344786. 86216] SEQ[15149547] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 17 : TIME[1231344786. 93216] SEQ[15149554] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 18 : TIME[1231344786.100217] SEQ[15149561] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 19 : TIME[1231344786.107218] SEQ[15149568] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 20 : TIME[1231344786.114213] SEQ[15149575] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 21 : TIME[1231344786.121212] SEQ[15149582] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 22 : TIME[1231344786.128210] SEQ[15149589] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 23 : TIME[1231344786.135210] SEQ[15149596] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 24 : TIME[1231344786.142208] SEQ[15149603] CHANGE[7] VARIATION[0]&lt;BR /&gt;Constant changes in initial sequence numbers observed in 21 out o&lt;BR /&gt;f 23 events.&lt;BR /&gt;Packet 1 : TIME[1231344839.390171] SEQ[15202848] CHANGE[N/A] VARIATION[N/A]&lt;BR /&gt;Packet 2 : TIME[1231344839.398113] SEQ[15202856] CHANGE[8] VARIATION[N/A]&lt;BR /&gt;Packet 3 : TIME[1231344839.405109] SEQ[15202863] CHANGE[7] VARIATION[1]&lt;BR /&gt;Packet 4 : TIME[1231344839.412108] SEQ[15202870] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 5 : TIME[1231344839.419107] SEQ[15202877] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 6 : TIME[1231344839.426107] SEQ[15202884] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 7 : TIME[1231344839.433106] SEQ[15202891] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 8 : TIME[1231344839.440104] SEQ[15202898] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 9 : TIME[1231344839.447107] SEQ[15202905] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 10 : TIME[1231344839.454102] SEQ[15202912] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 11 : TIME[1231344839.461101] SEQ[15202919] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 12 : TIME[1231344839.468111] SEQ[15202926] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 13 : TIME[1231344839.475101] SEQ[15202933] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 14 : TIME[1231344839.482098] SEQ[15202940] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 15 : TIME[1231344839.489096] SEQ[15202947] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 16 : TIME[1231344839.496095] SEQ[15202954] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 17 : TIME[1231344839.503094] SEQ[15202961] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 18 : TIME[1231344839.510093] SEQ[15202968] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 19 : TIME[1231344839.517100] SEQ[15202975] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 20 : TIME[1231344839.524091] SEQ[15202982] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 21 : TIME[1231344839.531089] SEQ[15202989] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 22 : TIME[1231344839.538089] SEQ[15202996] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 23 : TIME[1231344839.545088] SEQ[15203003] CHANGE[7] VARIATION[0]&lt;BR /&gt;Packet 24 : TIME[1231344839.552088] SEQ[15203010] CHANGE[7] VARIATION[0]&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Jan 2009 13:09:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/hp-ilo-1-93-and-older-predictable-tcp-initial-sequence-numbers/m-p/4336664#M4063</guid>
      <dc:creator>askotamm</dc:creator>
      <dc:date>2009-01-13T13:09:27Z</dc:date>
    </item>
  </channel>
</rss>

