<?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 Re: ASA leaking internal IP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130326#M1072625</link>
    <description>&lt;P&gt;This are our current alerts from the SIEM. All the destinations shows private IP now.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 04 Aug 2020 18:05:46 GMT</pubDate>
    <dc:creator>Brianoh733</dc:creator>
    <dc:date>2020-08-04T18:05:46Z</dc:date>
    <item>
      <title>ASA leaking internal IP</title>
      <link>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130259#M1072617</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We had a external pen test done and we were told that our firewall is leaking internal IP address. (Waiting for the official report)&lt;/P&gt;&lt;P&gt;I started gathering some logs and did find nmap from external to internal host. (Source was public IP and destination was our internal IP)&lt;/P&gt;&lt;P&gt;I am a beginner level and I have checked ASA and I do not find any holes.&lt;/P&gt;&lt;P&gt;Can someone please point me in right direction.&lt;/P&gt;&lt;P&gt;We have one to one static NAT for our public facing services. ASA 5515&lt;/P&gt;&lt;P&gt;Attach is a screenshot from PCAP file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Brian&lt;/P&gt;</description>
      <pubDate>Tue, 04 Aug 2020 16:29:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130259#M1072617</guid>
      <dc:creator>Brianoh733</dc:creator>
      <dc:date>2020-08-04T16:29:42Z</dc:date>
    </item>
    <item>
      <title>Re: ASA leaking internal IP</title>
      <link>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130288#M1072619</link>
      <description>&lt;P&gt;More than once I have seen external "pen tests" report false positives. If you can share more details we can have a look at it.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Aug 2020 17:04:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130288#M1072619</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-08-04T17:04:23Z</dc:date>
    </item>
    <item>
      <title>Re: ASA leaking internal IP</title>
      <link>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130292#M1072620</link>
      <description>Private IPs are not routable over internet. To confirm that the responses&lt;BR /&gt;are from your actual hosts use -sV option in nmap. This will fingerprint&lt;BR /&gt;the service.&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Aug 2020 17:06:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130292#M1072620</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2020-08-04T17:06:40Z</dc:date>
    </item>
    <item>
      <title>Re: ASA leaking internal IP</title>
      <link>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130324#M1072624</link>
      <description>&lt;P&gt;Attach file is a report from Nessus scan. I ran from public internet and targeted one of our public server.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Aug 2020 18:04:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130324#M1072624</guid>
      <dc:creator>Brianoh733</dc:creator>
      <dc:date>2020-08-04T18:04:13Z</dc:date>
    </item>
    <item>
      <title>Re: ASA leaking internal IP</title>
      <link>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130326#M1072625</link>
      <description>&lt;P&gt;This are our current alerts from the SIEM. All the destinations shows private IP now.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Aug 2020 18:05:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130326#M1072625</guid>
      <dc:creator>Brianoh733</dc:creator>
      <dc:date>2020-08-04T18:05:46Z</dc:date>
    </item>
    <item>
      <title>Re: ASA leaking internal IP</title>
      <link>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130335#M1072626</link>
      <description>Hi, most likely this is from your isp proxy instead of your hosts.&lt;BR /&gt;&lt;BR /&gt;Run nmap -n -v -sT -sV ##ip### -p 80,443&lt;BR /&gt;&lt;BR /&gt;See if the response match the version of your iis/Apache&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Aug 2020 18:27:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130335#M1072626</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2020-08-04T18:27:40Z</dc:date>
    </item>
    <item>
      <title>Re: ASA leaking internal IP</title>
      <link>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130350#M1072628</link>
      <description>&lt;P&gt;I ran the one nmap from a system on public internet targeting our web server public IP and I ran second nmap from a system inside our network targeting our webserver internal IP.&lt;/P&gt;&lt;P&gt;Both the results were same.&lt;/P&gt;&lt;P&gt;PORT STATE SERVICE VERSION&lt;BR /&gt;80/tcp open http Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP)&lt;BR /&gt;443/tcp open ssl/http Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP)&lt;BR /&gt;Service Info: OS: Windows; CPE: cpe:/o:microsoft:windows&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Aug 2020 19:06:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130350#M1072628</guid>
      <dc:creator>Brianoh733</dc:creator>
      <dc:date>2020-08-04T19:06:23Z</dc:date>
    </item>
    <item>
      <title>Re: ASA leaking internal IP</title>
      <link>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130586#M1072640</link>
      <description>&lt;P&gt;I did the NMAP scan from public internet to our public facing server public IP and capture the logs from my ASA.&lt;/P&gt;&lt;P&gt;The logs on ASA showed my laptop public IP as source but showed my public facing server private IP as destination.&lt;/P&gt;&lt;P&gt;That's probably cause of NAT?&lt;/P&gt;&lt;P&gt;Is that a normal for ASA so show private IP of my public server as destination under the logs? Rather than public IP on which NMAP was ran?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My SIEM get's logs from ASA and since ASA has destination IP as private IP, my SIEM alerts me of an External to Internal one on one scan.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Brian.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2020 06:18:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-leaking-internal-ip/m-p/4130586#M1072640</guid>
      <dc:creator>Brianoh733</dc:creator>
      <dc:date>2020-08-05T06:18:42Z</dc:date>
    </item>
  </channel>
</rss>

