CVE-2018-20222
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 · uneditedXXE issue in Airsonic before 10.1.2 during parse.
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 confidenceAn XML External Entity (XXE) vulnerability in Airsonic media server versions before 10.1.2 allows attackers to exploit the XML parser during document parsing. This can enable disclosure of sensitive files from the server, SSRF attacks, or denial of service through maliciously crafted XML input with external entity references.
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< 10.1.2CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Confirm Airsonic is installedCheck for running Airsonic process (look for 'airsonic' in process list) or locate Airsonic installation directoryAffected if Airsonic software is present on the system
-
Identify installed Airsonic versionCheck the Airsonic web interface About page, or examine the airsonic.war filename/version in the installation directory, or review startup logs for version informationAffected if Version displayed is below 10.1.2 (e.g., 10.1.1, 10.1.0, or any version prior to 10.1.2)
-
Determine if XML upload/import features are exposedReview Airsonic configuration for enabled import features that parse XML (such as playlist import, podcast import, or media scanning features that accept XML input)Affected if XML parsing features are accessible to users or unauthenticated attackers
If Airsonic is installed with a version lower than 10.1.2 and XML input can be submitted through available features, the system is vulnerable to XXE attacks.
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 · scoped10.1.2
Upgrade Airsonic to version 10.1.2 or later which contains the fix for the XXE vulnerability. If immediate upgrade is not possible, disable external entity processing in the XML parser configuration as a temporary workaround.
10.1.2
- 1. Back up your current Airsonic installation and database before proceeding
- 2. Download Airsonic version 10.1.2 from the official GitHub releases page (github.com/airsonic/airsonic/releases)
- 3. Stop the running Airsonic service
- 4. Replace the existing Airsonic WAR file and libraries with version 10.1.2
- 5. Deploy the new WAR file to your application server (Tomcat, Jetty, etc.)
- 6. Start the Airsonic service
- 7. Verify the application starts successfully and XML parsing functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20222 — 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-20222 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