CVE-2024-57360
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 · uneditedhttps://www.gnu.org/software/binutils/ nm >=2.43 is affected by: Incorrect Access Control. The type of exploitation is: local. The component is: `nm --without-symbol-version` function.
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 confidenceThe GNU binutils nm tool version 2.43 and later contains an incorrect access control vulnerability in the --without-symbol-version function. This local vulnerability allows unauthorized access to symbol information that should be restricted, potentially exposing sensitive metadata about compiled binaries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
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.
-
Check nm tool versionRun 'nm --version' or 'nm -V' to obtain the installed version number of the nm binaryAffected if The reported version is 2.43 or higher (any version from 2.43 onward is within the affected range)
-
Verify binutils package versionCheck your system's package manager for binutils version (e.g., 'dpkg -l binutils' on Debian/Ubuntu, 'rpm -q binutils' on RHEL/CentOS, or 'brew list binutils --version' on macOS)Affected if The binutils package version installed is 2.43 or later
-
Identify scripts using --without-symbol-versionSearch for usage of the --without-symbol-version flag in scripts, build configurations, or tooling by running: grep -r 'without-symbol-version' /path/to/search or manually inspecting nm invocations in your build pipelineAffected if The --without-symbol-version option is used in any automated or manual nm commands in the environment
-
Check nm binary permissions and ownershipRun 'ls -la $(which nm)' to verify who has execute access to the nm binary, and review any ACLs or capabilities set on the binaryAffected if The nm binary is executable by unprivileged users or groups beyond the intended audience
You are affected if the installed binutils nm version is 2.43 or later AND the --without-symbol-version functionality is accessible to unauthorized users or used in your environment.
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 dataUpgrade binutils to a version where the access control issue in nm --without-symbol-version is fixed, or apply vendor-supplied patches. If immediate upgrade is not feasible, restrict access to the nm binary and monitor its usage.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57360 — 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-2024-57360 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