dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-49849

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
An Out-of-bounds Read 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

This is an out-of-bounds read vulnerability in the parsing of PRJ files. The vulnerability stems from insufficient validation of user-supplied data during file parsing, allowing attackers to read and write past the boundaries of allocated memory structures, leading to memory corruption.

MitigationImplement rigorous bounds checking and validation of all user-supplied data fields within the PRJ file parsing logic to prevent out-of-bounds memory access. Users should avoid opening untrusted PRJ files until a patch is applied.

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 products that process PRJ files
    Search installed software for applications known to handle .prj file format (e.g., engineering, CAD, or project management software). Use 'Get-Process' or check Program Files directories for product names.
    Affected if A product that parses PRJ files is installed and the vulnerable parsing code is present in that version
  2. Determine the installed version of the PRJ-handling software
    Run the application's built-in 'About' dialog, check the executable properties (right-click > Properties > Details), or use 'wmic product get name,version' if available. Compare the version number to any vendor advisory.
    Affected if The installed version matches or falls within an affected version range if published by the vendor
  3. Verify if PRJ file import or parsing functionality is enabled
    Check application settings, preferences, or configuration menus for file import/parsing options. Look for PRJ-specific modules, plugins, or extensions that may be loaded.
    Affected if PRJ parsing is an active feature and the vulnerable code path can be triggered by opening a malicious PRJ file
  4. Review security and application logs for PRJ-related errors or crashes
    Examine Windows Event Viewer (Application and System logs), application-specific log directories, or debug logs for entries mentioning PRJ file parsing failures, access violations, or memory errors.
    Affected if Recent logs show crashes or exceptions when processing PRJ files, which may indicate attempted exploitation
  5. Inspect running processes and memory for PRJ parser activity
    Use Process Explorer or Task Manager to observe the process handling PRJ files. Check if the process shows unusual memory consumption patterns or access violations.
    Affected if A PRJ-handling process exhibits abnormal behavior or memory corruption indicators when processing PRJ files

You are affected if you have software that parses PRJ files and the installed version contains the vulnerable parsing code, particularly if the PRJ import feature is actively used.

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

Implement rigorous bounds checking and validation of all user-supplied data fields within the PRJ file parsing logic to prevent out-of-bounds memory access. Users should avoid opening untrusted PRJ files until a patch is applied.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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