dbcve.org
Netweaver Application Server JavaApplication · Sap

CVE-2022-41262

MEDIUM · 6.1 CVSS v3.1 Published 2022-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Due to insufficient input validation, SAP NetWeaver AS Java (HTTP Provider Service) - version 7.50, allows an unauthenticated attacker to inject a script into a web request header. On successful exploitation, an attacker can view or modify information causing a limited impact on the confidentiality and integrity of the application.

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 confidence

Insufficient input validation in SAP NetWeaver AS Java HTTP Provider Service version 7.50 allows an unauthenticated attacker to inject malicious script into web request headers. This header injection can lead to reflected script execution, enabling attackers to view or modify information with limited impact on confidentiality and integrity.

MitigationApply the SAP security patch for CVE-2022-41262 and implement server-side input validation on all HTTP request headers to reject special characters. If immediate patching is not possible, consider web application firewall rules to filter malicious header payloads.

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
Netweaver Application Server JavaApplication
Affected:= 7.50

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SAP NetWeaver AS Java installation
    Locate and inspect the SAP NetWeaver Java installation directory, typically under /usr/sap/<SID>/<instance>/j2ee or check SAP Manage ment Console (MMC) or SAP LMDB for installed software components. Use transaction code SM51 in SAP GUI or check the SAR file/sapcar extraction logs for version confirmation.
    Affected if The system has SAP NetWeaver Application Server Java installed with version 7.50 exactly
  2. Identify the exact NetWeaver Java version
    Execute command 'java -jar <DMIDOCS>/sap.com~tc~lm~version~impl.jar' or check SAP startup logs in work directory for version string '7.50'. Alternatively, access SAP NWA (NetWeaver Administrator) at https://<host>:<port>/nwa and navigate to Configuration > Infrastructure > System Information to view installed product version.
    Affected if The installed version is exactly 7.50 (version 7.50, not higher or lower
  3. Verify HTTP Provider Service is running
    Access SAP NetWeaver Administrator (NWA) at https://<host>:<port>/nwa, navigate to Operations > Systems > Services and locate 'HTTP Provider Service' (service name: sap.com/tc~pdu~httpprovider). Check if status shows 'Running' or execute command 'jcontrol -show -process <instance> | grep -i httpprovider' in the SAP instance directory.
    Affected if HTTP Provider Service is enabled and running on the affected system
  4. Confirm web container is accessible
    Test connectivity to the SAP Java web container by accessing common endpoints such as https://<host>:<port>/sap/bc/rest/ or http://<host>:<port>/webdynpro/welcome. Use tools like curl or browser to verify HTTP response is received from the NetWeaver Java HTTP ports (default 5<instance>00, e.g., 50000 for instance 00).
    Affected if The HTTP Provider Service is exposed to network and accepts web requests

Your system is affected only if SAP NetWeaver AS Java version 7.50 is installed AND the HTTP Provider Service is running and accessible via HTTP/HTTPS endpoints, allowing external web request headers to be processed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the SAP security patch for CVE-2022-41262 and implement server-side input validation on all HTTP request headers to reject special characters. If immediate patching is not possible, consider web application firewall rules to filter malicious header payloads.

Fix this in Netweaver Application Server Java Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41262 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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