CVE-2022-27193
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 · uneditedCVRF-CSAF-Converter before 1.0.0-rc2 resolves XML External Entities (XXE). This leads to the inclusion of arbitrary (local) file content into the generated output document. An attacker can exploit this to disclose information from the system running the converter.
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 CVRF-CSAF-Converter before version 1.0.0-rc2 is vulnerable to XML External Entity (XXE) injection. When processing XML input files, the converter resolves external entities, allowing attackers to include arbitrary local file content into generated output documents by crafting malicious XML with entity references pointing to local system files.
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= 1.0.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
- 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.
-
Verify Cvrf Csaf Converter is installedLocate the cvrf-csaf-converter tool on the system, typically found via package manager, Python pip list, or by searching for the executable in common pathsAffected if The tool is installed and present on the system
-
Identify the installed versionRun the converter with version flag (e.g., --version or -v) or check via package manager (pip show cvrf-csaf-converter) to determine the exact version numberAffected if Version equals 1.0.0 exactly (the only version explicitly listed as affected)
-
Confirm XML input processing is in useReview logs, scripts, or automation that invoke the converter to process XML input files, as the XXE flaw only triggers when the converter parses XMLAffected if The converter is actively processing XML input files from untrusted or external sources
-
Check XML parser configurationInspect the converter configuration files or source code to determine whether external entity resolution is enabled in the XML parser settingsAffected if External entity resolution is enabled (default vulnerable state in version 1.0.0)
A user is affected if Cvrf Csaf Converter version 1.0.0 is installed and is being used to process XML input files with external entity resolution enabled in the 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.
dbcve · scopedUpgrade to version 1.0.0-rc2 or later which contains the XXE fix. If immediate upgrade is not feasible, disable external entity resolution in the XML parser configuration or implement strict input validation for XML files before processing.
1.0.0-rc2 or later
- Upgrade CVRF-CSAF-Converter to version 1.0.0-rc2 or a later stable release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27193 — 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-27193 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