CVE-2022-35298
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 NetWeaver Enterprise Portal (KMC) - version 7.50, does not sufficiently encode user-controlled inputs, resulting in Cross-Site Scripting vulnerability. KMC servlet is vulnerable to XSS attack. The execution of script content by a victim registered on the portal could compromise the confidentiality and integrity of victim’s web browser session.
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 confidenceSAP NetWeaver Enterprise Portal version 7.50 contains a reflected XSS vulnerability in the KMC (Knowledge Management) servlet. User-supplied input to the servlet is not properly encoded, allowing an authenticated attacker to inject malicious JavaScript that executes in the browser sessions of other portal users.
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= 7.50CVSS 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 NetWeaver Enterprise Portal versionCheck the installed SAP NetWeaver Enterprise Portal version. This can typically be found in the SAP system information, the SAP Management Console, or by querying the SAP system via transaction SM37 or checking the SAR file/version metadata during installation. Confirm the exact version string shows 7.50.Affected if The installed version is exactly 7.50 (any patch level of 7.50). Versions other than 7.50 are not affected by this specific CVE.
-
Confirm KMC servlet is accessibleIdentify whether the Knowledge Management (KMC) servlet is deployed and accessible in the portal. This servlet is typically accessed via URLs containing /kmc/ or similar paths under the Enterprise Portal context. Check the SAP NetWeaver Administrator or the web container configuration for deployed servlets.Affected if The KMC servlet is deployed and accessible to authenticated users. If KMC is not installed or is completely disabled, the attack surface does not exist.
-
Review KMC servlet request patterns in access logsExamine SAP NetWeaver HTTP access logs (typically found in the work directory or via transaction SM37 for ICM logs) for requests to the KMC servlet. Look for requests containing unencoded script tags, javascript: URIs, or event handler attributes in query parameters.Affected if Requests to the KMC servlet contain unsanitized user input in URL parameters, especially script tags or HTML markup that could indicate exploitation attempts or successful injection.
-
Verify authentication configuration for portal accessCheck the SAP Enterprise Portal authentication configuration to confirm that user authentication is required for accessing the KMC servlet. This vulnerability requires an authenticated attacker, so verify that anonymous access to KMC is not enabled.Affected if Authenticated access is required (attacker must have valid portal credentials). If the KMC servlet allows anonymous access, the exploitation门槛 is lower, though the CVE specifies authenticated attackers.
You are affected if you are running SAP NetWeaver Enterprise Portal version 7.50 and the KMC servlet is deployed and accessible to authenticated portal users.
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 relevant SAP Security Note to patch the KMC servlet, ensuring all user-controlled inputs are properly validated and output-encoded. Alternatively, configure web application firewall rules to filter malicious script patterns in KMC requests.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35298 — 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-35298 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