CVERadar
MEDIUM · CVSS 3.1 4Public PoCEPSS 32.15% (p98)Threat level 34

CVE-1999-0524: CVE-1999-0524: ICMP information such as (1) netmask and (2) timestamp is allowed from arbitrary hosts.

apple · mac os x · NVD published 1997-08-01 · posted 2024-11-25 · last modified 2026-06-17

What it is

ICMP information such as (1) netmask and (2) timestamp is allowed from arbitrary hosts.

WeaknessCWE-200
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N (source: 134c704f-9b21-4f2e-91b3-4a467353bcc0)
ATT&CK tacticsCollection

Exploitation evidence

First exploit evidence seen: 2024-11-25 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

3 public repositories from 3 accounts, first seen 2024-11-25. Most starred: threatlabindonesia/CVE-1999-0524-ICMP-Timestamp-and-Address-Mask-Request-Exploit (3 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

How to fix it

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

MITRE ATT&CK mitigations for this chain

  • M1057 Data Loss Prevention (for T1005) : Data loss prevention can restrict access to sensitive data and detect sensitive data that is unencrypted.

Detection Generic guidance

  • Collection: Watch for bulk reads of databases, file shares or mailboxes by the affected service.

Response checklist Generic guidance

  1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
  2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
  3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
  4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Sources