dbcve.org
Netweaver Process IntegrationApplication · Sap

CVE-2022-41271

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

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
An unauthenticated user can attach to an open interface exposed through JNDI by the Messaging System of SAP NetWeaver Process Integration (PI) - version 7.50. This user can make use of an open naming and directory API to access services that could perform unauthorized operations. The vulnerability affects local users and data, leading to a considerable impact on confidentiality as well as availability and a limited impact on the integrity of the application. These operations can be used to: * Read any information * Modify sensitive information * Denial of Service attacks (DoS) * SQL Injection

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

An unauthenticated attacker can connect to an open JNDI interface exposed by SAP NetWeaver PI 7.50's Messaging System. This allows access to directory services without authentication, enabling unauthorized data access, modification, SQL injection, and denial of service.

MitigationApply available SAP security patches for this vulnerability and restrict network access to the JNDI messaging interface to prevent unauthenticated access.

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 Process IntegrationApplication
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
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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 checks

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

  1. Verify SAP NetWeaver PI version
    Check the installed SAP NetWeaver Process Integration version. On the SAP system, use transaction SM51 or check the kernel version details. The vulnerability affects only version 7.50 exactly.
    Affected if The installed version is exactly 7.50 (not higher or lower)
  2. Confirm Messaging System is running
    Check if the SAP NetWeaver PI Messaging System service is active. Use transaction SMMS or verify the Java cluster is running via SM51. The JNDI interface is part of this messaging system.
    Affected if The Messaging System service is running and accessible
  3. Identify JNDI listener port exposure
    Check for open ports associated with the JNDI interface. Review the SAP Java dispatcher configuration and the Messaging System port settings. Typical JNDI ports in SAP PI are in the 5xxxx range.
    Affected if The JNDI listener port (typically 5xxxx range) is open and exposed on the network
  4. Test unauthenticated JNDI access
    Attempt to connect to the JNDI interface from an unauthorized network location or system. Try accessing the JNDI service without providing SAP credentials to verify if authentication is enforced.
    Affected if The JNDI interface accepts connections without requiring authentication
  5. Review network accessibility
    Check if the JNDI port is bound to all network interfaces (0.0.0.0) rather than localhost only. Verify network accessibility through firewall rules or netstat listings showing the listening address.
    Affected if The JNDI port is accessible from external network addresses, not restricted to localhost only

A user is affected if they are running exactly SAP NetWeaver PI version 7.50 with the Messaging System's JNDI interface exposed and accessible without authentication on the network.

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 available SAP security patches for this vulnerability and restrict network access to the JNDI messaging interface to prevent unauthenticated access.

Fix this in Netweaver Process Integration Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41271 — 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-41271 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