CVE-2022-22529
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 · uneditedSAP Enterprise Threat Detection (ETD) - version 2.0, does not sufficiently encode user-controlled inputs which may lead to an unauthorized attacker possibly exploit XSS vulnerability. The UIs in ETD are using SAP UI5 standard controls, the UI5 framework provides automated output encoding for its standard controls. This output encoding prevents stored malicious user input from being executed when it is reflected in the UI.
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 confidenceSAP Enterprise Threat Detection version 2.0 contains a stored Cross-Site Scripting (XSS) vulnerability where user-controlled inputs are not sufficiently encoded before being rendered in the UI. Although SAP UI5 standard controls provide automatic output encoding, this protection does not prevent stored malicious input from executing when reflected back in the interface.
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= 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 SAP Enterprise Threat Detection versionCheck the installed version of SAP Enterprise Threat Detection in the system information or about screen. This vulnerability affects only version 2.0.Affected if The installed version is exactly 2.0 (no other versions are listed as affected)
-
Identify custom UI componentsReview any custom UI5 extensions, custom controls, or non-standard UI components added to the SAP Enterprise Threat Detection interface. These may bypass automatic output encoding.Affected if Custom UI components or non-standard controls that handle user input are present in the deployment
-
Locate stored user input fieldsIdentify areas in the application where user-controlled data is stored in the backend and then rendered back in the UI. Focus on data that persists across sessions.Affected if The application stores user input and reflects it back in the interface without re-encoding at render time
-
Check UI5 control usage for user data displayAudit how existing UI5 controls display stored user data, particularly in areas where data from external sources or other users is rendered.Affected if UI5 controls display stored data without additional output encoding at render time, allowing the stored input to execute when reflected
A user is affected if they are running SAP Enterprise Threat Detection version 2.0 and have custom UI components or store and display user-controlled data that gets rendered without proper output encoding at render time.
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 dataImplement proper output encoding for all user-controlled inputs at render time, particularly for stored data that gets displayed in the UI. Review custom UI components and non-standard controls that may bypass UI5's automatic encoding protection.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22529 — 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-22529 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