UntangleApplication · Untangle Project
CVE-2022-31471
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 · unediteduntangle is a python library to convert XML data to python objects. untangle versions 1.2.0 and earlier improperly restricts XML external entity references. By exploiting this vulnerability, a remote unauthenticated attacker may read the contents of local files.
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 confidenceThe untangle Python library versions 1.2.0 and earlier contains an XML External Entity (XXE) injection vulnerability due to improperly restricting XML external entity references. Attackers can supply malicious XML containing external entity declarations to read arbitrary local files from the system processing the XML.
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
UntangleApplication
<= 1.2.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Check if untangle library is installedRun 'pip show untangle' or 'pip list' to see if the untangle package is present in your Python environmentAffected if untangle package is not found in your Python environment
-
Determine the installed versionRun 'pip show untangle' and note the Version field, or compare output of 'pip list' against the affected range <= 1.2.0Affected if The installed version is 1.2.0 or earlier
-
Identify code using untangle to parse XMLSearch your codebase for 'import untangle' or 'from untangle import' statements, and identify where parse() or similar methods are called on untrusted XML inputAffected if Your application imports and uses untangle to process XML, especially from external or untrusted sources
You are affected if the untangle Python library version 1.2.0 or earlier is installed and your code uses it to parse XML from potentially untrusted sources.
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.
dbcve · scopedUpgrade untangle to a version that disables external entity processing, or configure the underlying XML parser to disable external entities and DTD processing before passing XML to untangle.
untangle version 1.2.1 or later
- Upgrade the untangle Python package to version 1.2.1 or later using pip: pip install --upgrade untangle
- Verify the upgrade was successful by running: pip show untangle
- After upgrading, ensure your application still functions correctly by running your test suite
- If you cannot upgrade immediately, you can mitigate by using defusedxml instead of untangle for parsing untrusted XML, or by sanitizing XML input before passing it to untangle
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Untangle
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31471 — 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-2022-31471 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