CVE-2022-25628
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 · uneditedAn authenticated user can perform XML eXternal Entity injection in Management Console in Symantec Identity Manager 14.4
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 confidenceThis is an XML External Entity (XXE) injection vulnerability in the Management Console of Symantec Identity Manager 14.4. An authenticated user can inject malicious external entity references into XML input processed by the application, potentially enabling disclosure of internal files, denial of service, or server-side request forgery (SSRF) attacks.
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= 14.3= 14.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify installed product versionCheck the installed version of Broadcom Symantec Identity Governance and Administration (SGA/Identity Manager) against the affected versions 14.3 and 14.4. Consult the product's about page, version file, or installation logs.Affected if The installed version is 14.3 or 14.4 specifically.
-
Confirm Management Console is accessibleDetermine whether the Management Console component is deployed and accessible in your environment. This is typically accessed via web interface on the application server.Affected if The Management Console is enabled and reachable over the network.
-
Identify XML input points in Management ConsoleReview the Management Console functionality to identify where XML input is processed. Common areas include configuration uploads, import features, or API endpoints that accept XML payloads.Affected if The Management Console accepts XML input without explicit disabling of external entity processing.
-
Check XML parser configurationExamine the application's XML parser configuration settings. Look for whether external entity processing and DTD processing are explicitly disabled in the XML parser used by the Management Console component.Affected if The XML parser has external entity or DTD processing enabled (default or unconfigured state).
You are affected if you have version 14.3 or 14.4 of Symantec Identity Governance And Administration running with the Management Console accessible and XML input accepted without disabled 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 dataApply the vendor patch for CVE-2022-25628 for Symantec Identity Manager 14.4. If no patch is available, disable external entity processing and DTD processing in the XML parser configuration within the Management Console component.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25628 — 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-25628 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