CVE-2018-1000825
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 · uneditedFreeCol version <= nightly-2018-08-22 contains a XML External Entity (XXE) vulnerability in FreeColXMLReader parser that can result in Disclosure of confidential data, denial of service, SSRF, port scanning. This attack appear to be exploitable via Freecol file.
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 · high confidenceFreeCol versions up to nightly-2018-08-22 contain an XML External Entity (XXE) vulnerability in the FreeColXMLReader parser. Attackers can exploit this by crafting malicious FreeCol game files containing external entity references, enabling unauthorized file access, SSRF, port scanning, or denial of service.
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 data<= 2018-08-22CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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 FreeCol versionRun FreeCol with --version flag, check the application about dialog, or examine the freecol JAR file for version metadataAffected if Version is <= 2018-08-22 (any nightly build on or before that date)
-
Locate FreeColXMLReader classFind the freecol JAR file and locate the FreeColXMLReader.class or source file within the codebaseAffected if The FreeColXMLReader class exists in the installation and is used for parsing game files
-
Determine XML parser configurationExamine the FreeColXMLReader source code or decompiled JAR to see how the XML parser (typically javax.xml.parsers.DocumentBuilder) is configured - check if DTD processing or external entity resolution is explicitly enabledAffected if The XML parser has features for external entity processing or DTD processing enabled rather than disabled
-
Identify game file parsing workflowObserve or log how FreeCol loads game save files - the FreeColXMLReader is invoked when loading .fsg or other game data filesAffected if FreeCol parses XML-based game files using FreeColXMLReader without input validation or disabling of external entities
A user is affected if they run FreeCol version 2018-08-22 or earlier and the application loads XML-based game files using the vulnerable FreeColXMLReader parser with external entity processing enabled.
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 and DTD processing in the XML parser configuration used by FreeColXMLReader, and validate or sanitize XML input before parsing.
- Consultation1.0 h
- Implementation3.0 h
- Testing2.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 $2,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000825 — 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-2018-1000825 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