CVE-2025-49848
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 · uneditedAn out-of-bounds write vulnerability exists within the parsing of PRJ files. The issues result from the lack of proper validation of user-supplied data, which can result in different memory corruption issues within the application, such as reading and writing past the end of allocated data structures.
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 confidenceAn out-of-bounds write vulnerability exists in the parsing of PRJ files due to insufficient validation of user-supplied data, leading to memory corruption where the application can read and write past the end of allocated data structures.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify software that parses PRJ files in your environmentReview installed applications and determine which programs handle .prj files. Common software includes GIS applications, CAD tools, or geospatial libraries. Check program menus or file associations for PRJ file support.Affected if Any software in your environment processes or imports PRJ files and the software version falls within the affected range (compare to vendor release notes if available)
-
Locate the vulnerable application versionCheck the installed version of the identified PRJ-parsing software. Typical methods: Help > About, software --version flag, or checking installed program details in system settings.Affected if The installed version matches the vulnerable version range for this CVE (if vendor has published specific versions)
-
Confirm PRJ file parsing is enabled or usedVerify whether the software has active PRJ file import or parsing functionality. Look for: file import dialogs supporting .prj extension, recent files list showing .prj, or active processing of geospatial/project files.Affected if PRJ file parsing feature is available and could be invoked by opening or importing a malicious PRJ file
-
Review recent PRJ file processing activityCheck application logs, recent files, or temp directories for evidence of PRJ file handling. On Windows: check %AppData% or program-specific log folders. On Linux/Unix: check ~/.config or program log directories.Affected if The application has recently processed PRJ files, indicating the parsing code path is active in your environment
You are affected if your environment contains software that parses PRJ files and that software's version is within the vulnerable range or has the PRJ parsing feature enabled and could process malicious files.
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 dataImplement strict bounds checking and proper validation of all user-supplied data during PRJ file parsing to prevent out-of-bounds memory access; consider sandboxing or input filtering as defense-in-depth.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49848 — 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-49848 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