CVE-2021-21517
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 · uneditedSRS Policy Manager 6.X is affected by an XML External Entity Injection (XXE) vulnerability due to a misconfigured XML parser that processes user-supplied DTD input without sufficient validation. A remote unauthenticated attacker can potentially exploit this vulnerability to read system files as a non-root user and may be able to temporarily disrupt the ESRS service.
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 confidenceSRS Policy Manager 6.X contains a misconfigured XML parser that processes user-supplied DTD input without proper validation, enabling XML External Entity (XXE) injection. A remote unauthenticated attacker can exploit this to read arbitrary system files as the non-root service account and potentially disrupt the ESRS 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= 6.6= 6.8.3= 6.9.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
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:L
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 installed SRS Policy Manager versionCheck the product version through the management console, about page, or installation directory metadata. Common locations include the install log, version.info file, or the admin UI help/about section.Affected if version equals 6.6, 6.8.3, or 6.9.0 exactly (these are the affected versions)
-
Confirm XML submission endpoints are accessibleLocate HTTP/HTTPS endpoints that accept XML input such as policy configuration import, XML-based API calls, or data submission forms. These are the entry points where the vulnerable XML parser processes user data.Affected if XML input endpoints are exposed to unauthenticated or low-privilege network users
-
Verify DTD processing is enabled in XML parserExamine the XML parser configuration files or settings that control DTD (Document Type Definition) and external entity processing. Look for parser settings related to 'external-general-entities', 'external-parameter-entities', or 'allow-dtd'.Affected if the XML parser is configured to process DTD declarations and external entities without validation (the vulnerability condition)
-
Check for unauthenticated XML input pathsReview network-accessible interfaces that accept XML without requiring authentication, such as public API endpoints, login forms with XML payloads, or policy import features accessible to anonymous users.Affected if unauthenticated users can submit XML content to the system
You are affected if running version 6.6, 6.8.3, or 6.9.0 AND the system exposes XML input endpoints to unauthenticated users with the XML parser configured to allow DTD/external entity processing.
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 or implement strict input validation to reject DTD declarations and external entity references in XML submissions.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21517 — 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-2021-21517 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