Network Data Loss PreventionApplication · Mcafee

CVE-2014-8533

HIGH · 7.5 CVSS v2.0 Published 2014-10-29
Fix available
A fix is available. Upgrade to after 9.2.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
McAfee Network Data Loss Prevention (NDLP) before 9.3 allows remote attackers to execute arbitrary code via vectors related to ICMP redirection.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

McAfee Network Data Loss Prevention (NDLP) versions prior to 9.3 contain a vulnerability that allows remote unauthenticated attackers to execute arbitrary code through malicious ICMP redirection packets. The ICMP redirection mechanism is exploited to inject and execute code on affected NDLP systems.

MitigationUpgrade McAfee NDLP to version 9.3 or later. As an interim defense-in-depth measure, filter or disable untrusted ICMP redirects at network perimeter devices and implement network segmentation to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Network Data Loss PreventionApplication
Affected:<= 9.2.2= 8.6= 9.2.0= 9.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed McAfee NDLP version
    Access the NDLP management console or use the product's built-in version check command (typically via the ePO console or running 'ndlp --version' from the NDLP installation directory). Check the About/Version section in the NDLP web interface if available.
    Affected if The installed version is 8.6, 9.2.0, 9.2.1, or any version <= 9.2.2 (versions prior to 9.3)
  2. Confirm NDLP is running as a network gateway or sensor
    Review the NDLP deployment configuration in the ePO console or NDLP management interface. Check if the system is configured in inline, bridge, or tap mode where it processes network traffic directly.
    Affected if NDLP is deployed in a mode where it processes ICMP traffic from untrusted network segments (inline/bridge/sensor modes)
  3. Verify ICMP redirection handling is enabled
    Check the NDLP network configuration settings for ICMP redirection handling or 'accept ICMP redirects' policy. This is typically found under Network Settings, Protocol Handling, or ICMP settings in the NDLP/ePO console.
    Affected if ICMP redirection packets from external or untrusted networks are allowed to be processed by NDLP (the setting is enabled or not explicitly disabled)
  4. Assess network exposure to untrusted ICMP sources
    Review firewall rules and network segmentation around the NDLP appliance. Determine if the NDLP interface handling external/partner traffic can receive ICMP redirection packets from non-trusted hosts or only from explicitly trusted gateways.
    Affected if The NDLP sensor/gateway interface can receive ICMP redirect packets from hosts other than trusted network infrastructure devices (routers/gateways)
  5. Check for recent ICMP-related events or anomalies
    Review NDLP event logs, system logs, or ePO events for unusual ICMP redirection traffic, especially ICMP type 5 (redirect) packets, or spikes in ICMP traffic around the time frame of potential exploitation.
    Affected if There are logged ICMP redirection packets from unexpected sources or anomalous ICMP traffic patterns

A system is affected if it runs McAfee NDLP version 9.2.2 or earlier (including 8.6, 9.2.0, 9.2.1) and is configured to process network traffic where ICMP redirection packets from untrusted sources can reach the NDLP sensor.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 9.2.2
Interim mitigation

Upgrade McAfee NDLP to version 9.3 or later. As an interim defense-in-depth measure, filter or disable untrusted ICMP redirects at network perimeter devices and implement network segmentation to limit exposure.

Fix this in Network Data Loss Prevention Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-8533 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-8533 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data