CVE-2010-2529
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 · uneditedUnspecified vulnerability in ping.c in iputils 20020927, 20070202, 20071127, and 20100214 on Mandriva Linux allows remote attackers to cause a denial of service (hang) via a crafted echo response.
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 confidenceA denial of service vulnerability exists in ping.c in the iputils package (versions 20020927 through 20100214) on Mandriva Linux. Remote attackers can send a crafted ICMP echo response packet that causes the ping utility to hang (likely entering an infinite loop or blocking state). The vulnerability is triggered upon processing the malicious echo response.
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= 20020927= 20070202= 20071127= 20100214CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify iputils package is installedRun 'rpm -q iputils' on Mandriva or check for /bin/ping binary existence with 'ls -l /bin/ping'Affected if The iputils package or ping binary is present on the system
-
Identify installed iputils versionRun 'rpm -q --queryformat "%{VERSION}-%{RELEASE}" iputils' or '/bin/ping -V' to obtain the version numberAffected if A version number is returned showing 20020927, 20070202, 20071127, or 20100214
-
Confirm version falls within vulnerable rangeCompare the installed version against the affected range 20020927 through 20100214Affected if The installed version is 20020927, 20070202, 20071127, or 20100214 (any version from 20020927 up to and including 20100214)
-
Check system is Mandriva LinuxRun 'cat /etc/mandriva-release' or 'lsb_release -id' to confirm the distributionAffected if The system is running Mandriva Linux with the vulnerable iputils version installed
The environment is affected if iputils version 20020927 through 20100214 is installed on a Mandriva Linux system, allowing untrusted ICMP echo responses to cause ping to hang.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate iputils to a patched version beyond 20100214. Alternatively, implement network-level filtering to block untrusted ICMP echo responses at the perimeter, or restrict ping access to trusted network sources.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2529 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-2529 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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