dbcve.org
Netweaver Application Server For JavaApplication · Sap

CVE-2022-27669

HIGH · 7.5 CVSS v3.1 Published 2022-04-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 use functions of XML Data Archiving Service of SAP NetWeaver Application Server for Java - version 7.50, to which access should be restricted. This may result in an escalation of privileges.

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 · moderate confidence

Unauthenticated users can access restricted functions in the XML Data Archiving Service of SAP NetWeaver Application Server for Java version 7.50. This improper access control allows privilege escalation by enabling unauthorized individuals to invoke administrative or privileged operations that should require authentication.

MitigationRestrict access to the XML Data Archiving Service functions by implementing proper authentication and authorization controls. Review and enforce role-based access restrictions on the affected service components.

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 For 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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Identify SAP NetWeaver AS for Java version
    Use SAP administration tools (SAP Management Console, SAP MMC, or 'smon' command) to retrieve the installed version of SAP NetWeaver Application Server for Java. Check the detailed system information or version display output.
    Affected if The installed version is exactly 7.50 (version 7.50 only)
  2. Locate XML Data Archiving Service
    Access the SAP NetWeaver Administrator (NWA) or SAP Configuration Wizard. Navigate to the services or components list and search for 'XML Data Archiving Service' or 'XML Data Archiving' to confirm its presence in the deployment.
    Affected if The XML Data Archiving Service is installed and listed as an active component
  3. Check service accessibility
    Attempt to access the XML Data Archiving Service endpoints (typically exposed via HTTP/HTTPS on the SAP Java server port) without providing credentials. Observe whether the service responds or returns data rather than redirecting to a login page or returning an authentication error.
    Affected if The service responds to unauthenticated requests with valid data or administrative options instead of requiring authentication
  4. Review service endpoint configuration
    Examine the SAP NetWeaver AS for Java configuration files (such as the deployment descriptor or service-specific XML configuration) related to the XML Data Archiving Service. Look for security constraints, authentication settings, or access control definitions.
    Affected if No authentication constraint is defined for the XML Data Archiving Service endpoints, or the security constraint is set to 'none'

You are affected if you run SAP NetWeaver Application Server for Java version 7.50 with the XML Data Archiving Service enabled and accessible without authentication.

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 access to the XML Data Archiving Service functions by implementing proper authentication and authorization controls. Review and enforce role-based access restrictions on the affected service components.

Recommended fix Moderate confidence
  1. 1. Access SAP Support Portal (support.sap.com) and search for security notes related to CVE-2022-27669
  2. 2. Identify and apply the relevant SAP Security Note that addresses this vulnerability in NetWeaver AS Java 7.50
  3. 3. After applying the patch, verify that unauthorized access to XML Data Archiving Service functions is properly restricted
  4. 4. Test that authentication and authorization controls are enforced for the affected components
  5. 5. Review user authorizations to ensure the principle of least privilege is applied

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

Fix this in Netweaver Application Server For Java Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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