This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 48%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESB%3C/text%3E%3C/svg%3E)
how to resolve this or do we have any information if we can restrict on firewall
yes, you can create a firewall rule for this one with the following settings:
Click on the newly created rule. In the protocol settings:
Let me try and get back to you
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 81%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENS%3C/text%3E%3C/svg%3E)
I have also the same problem.
Description: Nessus Vulnerability Information:
CVE-1999-0524 Name :ICMP Timestamp Request Remote Date Disclosure
Synopsis: It is possible to determine the exact time set on the remote host.
Descriptions: The remote host answers to an ICMP timestamp request. This allows an
attacker to know the date that is set on the targeted machine, which
may assist an unauthenticated, remote attacker in defeating time-based
authentication protocols.
Solution: "Filter out the ICMP timestamp requests (13), and the outgoing ICMP
timestamp replies (14)."
Please help here!
Thanks
Narendra
From the lab tests, we could see a response from the Private IP of the Firewall.
Can you share the results of PINGing the Azure Firewall from a VM in the same VNET?
Cheers,
Kapil
Hi Kapil,
Thanks for supporting.
We have window server2019 VM on premises base machine hyper VM and using the Fortinet Firewall not the Azure Firewall .
Thanks
Narendra,
I have applied the above firewall rules inbound and outbound but still Vulnerability opened.
We cannot comment on the behavior of a 3rd party firewall.
Please reach out to their forums or contact the 3rd party's support for more information on how to mitigate this
Cheers,
Kapil
@KapilAnanth-MSFT ,Rules applied in window server 2019 OS Firewall not the 3rd party firewall.
What I meant to say was - we cannot comment on the behavior of the Vulnerability alert.
Also, this thread is tagged as "Azure Firewall" - I would suggest you please post a new query with "Windows Network" tag so the appropriate SMEs can look into this
Cheers,
Kapil
Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I understand that you would like to know
We shall check this internally and get back to you soon.
Cheers,
Kapil
Hi @Shaweta Bhardwaj ,
From lab set up, we found that Azure Firewall's Private IP does not respond to ICMP traffic.
Cheers,
Kapil
Applied firewall rules