dbcve.org
BinutilsApplication · Gnu

CVE-2025-7545

HIGH · 7.8 CVSS v3.1 Published 2025-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
A vulnerability classified as problematic was found in GNU Binutils 2.45. Affected by this vulnerability is the function copy_section of the file binutils/objcopy.c. The manipulation leads to heap-based buffer overflow. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The patch is named 08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944. It is recommended to apply a patch to fix this issue.

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 · high confidence

Heap-based buffer overflow vulnerability in the copy_section function of binutils/objcopy.c in GNU Binutils 2.45 allows local attackers to cause memory corruption via specially crafted input files processed by objcopy.

MitigationApply patch 08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944 or upgrade to a fixed version of GNU Binutils. Since this is a local attack requiring user interaction, restrict usage of objcopy to trusted inputs and update binutils promptly.

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
BinutilsApplication
Affected:= 2.45

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

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

  1. Check if objcopy is installed
    Run 'which objcopy' or 'command -v objcopy' to locate the objcopy binary
    Affected if objcopy binary exists on the system
  2. Determine objcopy version
    Run 'objcopy --version' and note the version number displayed (typically first line)
    Affected if Version displayed is 2.45 exactly
  3. Verify copy_section function is reachable
    The vulnerability is triggered when objcopy processes a specially crafted input file using the copy_section function. Check if objcopy is used in any automated scripts or workflows that process external/untrusted input files
    Affected if objcopy is used to process files from untrusted sources or automated pipelines without input validation
  4. Confirm affected binary
    Run 'objcopy --help' to confirm the binary is from GNU Binutils and matches the affected version 2.45
    Affected if Binary is GNU Binutils objcopy version 2.45

A system is affected if objcopy from GNU Binutils version 2.45 is installed and used to process potentially untrusted input files

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply patch 08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944 or upgrade to a fixed version of GNU Binutils. Since this is a local attack requiring user interaction, restrict usage of objcopy to trusted inputs and update binutils promptly.

Recommended fix High confidence
  1. Obtain the patch commit 08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944 from the Binutils git repository (sourceware.org/git/binutils-gdb.git)
  2. Verify the patch applies cleanly to Binutils 2.45 source tree in binutils/objcopy.c
  3. Apply the patch using 'git apply' or by manually applying the diff
  4. Rebuild Binutils from source after applying the patch
  5. Verify the fix by rebuilding and testing objcopy with the vulnerable code path
  6. Replace the system-installed Binutils 2.45 with the patched version
Caveat Rebuilding Binutils from source may require ensuring all dependent build tools are available; ensure production systems use the patched binaries

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Binutils Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2025-7545 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