dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2025-49850

HIGH · 8.4 CVSS v4.0 Published 2025-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
No privileges

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 Heap-based Buffer Overflow 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 confidence

A heap-based buffer overflow vulnerability exists in the parsing of PRJ files due to insufficient validation of user-supplied data. Attackers can exploit this by crafting malicious PRJ files that cause the application to read or write beyond allocated memory boundaries, potentially leading to arbitrary code execution.

MitigationApply proper input validation and bounds checking during PRJ file parsing to ensure all user-supplied data is validated before use. Implement secure memory handling practices to prevent overflow conditions.

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
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify software that parses PRJ files
    Inventory your installed applications and determine which software handles .prj files in your environment. Common tools that may use PRJ files include GIS applications, project management tools, or CAD software. Check file associations and installed programs.
    Affected if PRJ file parsing software is present but version cannot be determined or falls within an unpatched range
  2. Determine the installed version of PRJ-processing software
    Run 'Get-ItemProperty' or check the program's properties via the installed software list to find the exact version number of the application that handles PRJ files.
    Affected if The installed version matches or predates any known vulnerable version range for this CVE
  3. Verify PRJ file parsing is enabled
    Check whether the software's PRJ file import/parsing feature is enabled in the application settings or configuration. Look for options related to file import, project file loading, or data import modules.
    Affected if PRJ file parsing functionality is enabled and accessible to users
  4. Inspect recent PRJ file access logs
    Review application logs, file access logs, or system event logs for recent instances of PRJ file processing. Check for any anomalous or unexpected PRJ file operations.
    Affected if There is evidence of processing untrusted or external PRJ files without verification
  5. Check for suspicious PRJ files in accessible directories
    Scan directories where PRJ files may be stored or received (download folders, shared drives, email attachments) for unexpected or unfamiliar PRJ files that may be maliciously crafted.
    Affected if Unknown or unexpected PRJ files from untrusted sources are present in the environment

You are likely affected if you have software that parses PRJ files and that software is running an unpatched version that processes user-supplied or external PRJ 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply proper input validation and bounds checking during PRJ file parsing to ensure all user-supplied data is validated before use. Implement secure memory handling practices to prevent overflow conditions.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49850 — 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-49850 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