CVE-2022-35170
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 does - versions 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, 7.50, not sufficiently encode user-controlled inputs over the network, resulting in reflected Cross-Site Scripting (XSS) vulnerability, therefore changing the scope of the attack. This leads to limited impact on confidentiality and integrity of data.
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 versions 7.10 through 7.50 contains a reflected Cross-Site Scripting (XSS) vulnerability where user-controlled inputs over the network are not properly encoded, allowing injection of malicious scripts.
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.10= 7.11= 7.20= 7.30= 7.31= 7.40= 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.
-
Confirm SAP NetWeaver Enterprise Portal installationIdentify if SAP NetWeaver Enterprise Portal is running in your environment. Check for SAP portal services, typically accessible via HTTP/HTTPS on ports commonly used by SAP Web Dispatcher (typically 80xx, 443xx, or 50000-50099). Look for portal login pages or SAP Enterprise Portal banners in HTTP response headers.Affected if SAP NetWeaver Enterprise Portal is installed and accessible over the network
-
Determine the installed portal versionAccess the SAP Enterprise Portal login page or system information endpoint. The version is often displayed in the login page footer, system information screen, or can be retrieved via SAP transaction code SM37 or by checking the SAP system properties. Compare your version against the affected list: 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50.Affected if The installed version matches any of: 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50
-
Identify exposed portal endpointsReview your network-facing SAP Enterprise Portal configuration. Identify which portal components and servlets are accessible over the network. Common entry points include the portal runtime, iView server, and various SAP transactions exposed through the web interface.Affected if Portal components that handle user input are exposed to untrusted network sources
-
Test for reflected input handlingLocate portal URLs that accept user-controlled parameters (query strings, form inputs, or path parameters). Submit benign test values in parameters and observe if those values are reflected unchanged in the response without proper encoding. Check for presence of special characters like <, >, " returned in the response body.Affected if User-supplied input is reflected in HTTP responses without encoding or sanitization
You are affected if SAP NetWeaver Enterprise Portal versions 7.10 through 7.50 is installed, exposed to the network, and user-controlled inputs are reflected without encoding in portal web responses.
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 available SAP security patches for this vulnerability and implement proper output encoding for all user-controlled inputs in the affected portal components.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35170 — 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-35170 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