CVE-2023-25955
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 · uneditedNational land numerical information data conversion tool all versions improperly restricts XML external entity references (XXE). By processing a specially crafted XML file, arbitrary files on the PC may be accessed by an attacker.
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 confidenceThe National land numerical information data conversion tool all versions contains an XXE vulnerability where the XML parser does not properly restrict external entity references. An attacker can craft a malicious XML file that, when processed by the tool, allows reading arbitrary files from the victim's filesystem.
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 dataall versionsCVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Confirm the MLIT National Land Numerical Information Data Conversion Tool is installedSearch for the tool in the system application list, installation directory, or by searching for executables with names related to 'National Land Numerical Information' or 'MLIT data conversion'. Check common installation paths for government or geospatial tools.Affected if The tool is found installed on the system
-
Identify XML input files processed by the toolReview the tool's documentation or examine sample input files in the installation directory. Look for .xml file extensions or XML file format specifications associated with the tool.Affected if The tool processes XML files as input
-
Check XML parser configuration for external entity settingsLocate configuration files, settings, or documentation that control XML parsing behavior. Look for flags or options related to 'external entities', 'DTD processing', 'entity expansion', or 'XXE protection'. Check if the parser has security settings explicitly disabled or left at default insecure values.Affected if External entity processing is enabled or not explicitly disabled in the parser configuration
-
Test for XXE vulnerability with a benign XML payloadCreate a test XML file with an external entity reference pointing to a non-sensitive file (such as a text file in the tool's directory) and process it through the tool. Observe if the external entity is resolved and its content included in the output.Affected if The tool resolves and includes content from external entities in the processed output
A user is affected if the MLIT National Land Numerical Information Data Conversion Tool is installed and processes XML files with external entity processing enabled in the XML parser configuration.
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 dataDisable external entity processing in the XML parser configuration and implement input validation for XML files before parsing. Users should avoid processing untrusted XML files until a patch is applied.
- Consultation8.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25955 — 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-2023-25955 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