CVE-2025-60751
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 · uneditedGeographicLib 2.5 is vulnerable to Buffer Overflow in GeoConvert DMS::InternalDecode.
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 confidenceGeographicLib 2.5 contains a buffer overflow vulnerability in the GeoConvert utility's DMS::InternalDecode function, which parses geographic coordinate strings in degrees-minutes-seconds format. An attacker could potentially exploit this by providing specially crafted DMS input to cause memory corruption.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify if GeographicLib is installedSearch for GeographicLib installation directories, check package managers (apt, yum, brew, conda), or look for libGeographic or GeoConvert binaries in common paths (/usr/bin, /usr/local/bin, /opt)Affected if GeographicLib libraries or utilities are present on the system
-
Check if GeoConvert utility is presentLocate the GeoConvert binary using 'which GeoConvert' or 'find / -name GeoConvert -type f 2>/dev/null'Affected if GeoConvert executable exists and can be invoked
-
Determine the installed GeographicLib versionRun 'GeoConvert --version' or check library version via 'ldd' on any GeographicLib-linked binaries, or inspect the library file metadataAffected if Version is 2.5 or falls within the 2.x range without confirmed patch
-
Verify DMS coordinate parsing is in useReview application code or scripts that invoke GeoConvert to see if DMS format input (e.g., '40°26′46″N') is being processedAffected if User-supplied or external DMS-formatted coordinate strings are passed to GeoConvert
-
Inspect input handling for DMS stringsExamine how DMS input reaches GeoConvert: check for direct command-line invocation, API calls to DMS::InternalDecode, or configuration files accepting DMS coordinatesAffected if DMS input is not validated for length or format before being passed to the parser
A system is affected if it runs GeographicLib 2.5 (or unpatched 2.x) and processes DMS-formatted coordinate strings through GeoConvert without input validation.
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 to a patched version of GeographicLib if available, or implement strict input validation and length limits on DMS coordinate strings passed to GeoConvert to prevent overflow conditions.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60751 — 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-2025-60751 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