dbcve.org
Netweaver Process IntegrationApplication · Sap

CVE-2022-41272

HIGH · 8.6 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 →
95/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 attacker over the network can attach to an open interface exposed through JNDI by the User Defined Search (UDS) of SAP NetWeaver Process Integration (PI) - version 7.50 and make use of an open naming and directory API to access services which can be used to perform unauthorized operations affecting users and data across the entire system. This allows the attacker to have full read access to user data, make limited modifications to user data, and degrade the performance of the system, leading to a high impact on confidentiality and a limited impact on the availability 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

An unauthenticated network attacker can exploit an open JNDI interface exposed through the User Defined Search (UDS) component in SAP NetWeaver Process Integration 7.50. This allows the attacker to access naming and directory services to perform unauthorized operations, granting full read access to user data and limited modification capabilities across the system.

MitigationRestrict network access to the UDS interface, disable or secure the exposed JNDI endpoint, and apply relevant SAP security patches. Implement proper authentication and authorization controls on the JNDI 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
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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

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. Identify the SAP NetWeaver Process Integration version
    Use SAP transaction code SM51 to display the installed software components and their versions, or check the SAP Support Portal for the installed PI/PO version. Alternatively, query the SAP system landscape directory (SLD) or use SAP NWA (NetWeaver Administrator) -> System -> Overview to view the installed product version.
    Affected if The installed version is exactly 7.50 (SAP NetWeaver Process Integration 7.50)
  2. Verify the User Defined Search (UDS) component is deployed
    Check the SAP system for UDS configuration via transaction code UDC (UDS Configuration) or via SAP NWA -> Configuration -> Infrastructure -> Application Modules. Look for the UDS module status.
    Affected if The UDS component is active or deployed on the system
  3. Confirm network exposure of the JNDI interface
    Review SAP UDS configuration files (such as uds.properties or uds-config.xml typically found in the PI/PO configuration directory) to identify the JNDI listener port and endpoint URL. Use network scanning tools (netstat, nmap) or check SAP UDS logs to verify if the JNDI endpoint is listening on accessible network interfaces.
    Affected if The JNDI interface configured for UDS is bound to a network-accessible IP/port rather than localhost only
  4. Review UDS access controls
    Check the SAP UDS security configuration for authentication settings on the JNDI endpoint. Inspect the uds-security.xml or equivalent configuration file to verify whether anonymous or unauthenticated access is permitted to the JNDI naming services.
    Affected if Anonymous or unauthenticated access is allowed to the JNDI interface

A system is affected if it runs SAP NetWeaver Process Integration version 7.50 AND has the UDS component with its JNDI interface exposed to the network without proper authentication controls.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to the UDS interface, disable or secure the exposed JNDI endpoint, and apply relevant SAP security patches. Implement proper authentication and authorization controls on the JNDI interface.

Recommended fix Moderate confidence

SAP NetWeaver Process Integration 7.50 with corresponding security patch (contact SAP Support for exact patch number)

  1. Check SAP Note 3123416 for this specific CVE to obtain the relevant security patch
  2. Contact SAP Support to request the latest security patch for NetWeaver PI 7.50
  3. Review all SAP Notes referenced in the security advisory for additional required patches
  4. After patching, verify the UDS service is no longer exposed on unprotected network interfaces
  5. If immediate patching is not possible, restrict network access to the JNDI-exposed interfaces using firewall rules or network segmentation
Caveat Review SAP Note 3123416 for any known compatibility issues or post-patch configuration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netweaver Process Integration Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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