dbcve.org
Netweaver Development InfrastructureApplication · Sap

CVE-2022-29618

MEDIUM · 6.1 CVSS v3.1 Published 2022-06-14
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 Development Infrastructure (Design Time Repository) - versions 7.30, 7.31, 7.40, 7.50, allows an unauthenticated attacker to inject script into the URL and execute code in the user’s browser. On successful exploitation, an attacker can view or modify information causing a limited impact on 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 · moderate confidence

This is a reflected Cross-Site Scripting (XSS) vulnerability in SAP NetWeaver Development Infrastructure's Design Time Repository component. Due to insufficient input validation, unauthenticated attackers can inject malicious JavaScript into URLs, which executes in victim users' browsers when they access the crafted URL.

MitigationApply the relevant SAP security note/patch for CVE-2022-29618. Implement proper input validation and output encoding for all URL parameters to prevent script injection.

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 Development InfrastructureApplication
Affected:= 7.30= 7.31= 7.40= 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. Identify the SAP NetWeaver Development Infrastructure version
    Execute the SAP kernel version check command: 'sapcontrol -nr <instance_number> -function GetVersion' or check the SAP Note 1718410 for version identification methods. Alternatively, check the 'sapkernel<exe>' version in the /sapmnt/<SID>/exe directory.
    Affected if The installed version matches 7.30, 7.31, 7.40, or 7.50 exactly.
  2. Confirm Design Time Repository component is enabled
    Access the DTR web interface by navigating to the SAP NetWeaver Administration (NWA) or DTR URL endpoint. Typically found at: http://<host>:<port>/dtr or through the SAP NetWeaver Developer Studio connection.
    Affected if The Design Time Repository web interface is accessible without authentication.
  3. Verify the DTR URL parameters are exposed
    Inspect the DTR web application's URL structure by logging into the DTR interface and observing how parameters are passed in the browser address bar (e.g., navigation links, search parameters).
    Affected if URL parameters are visible in the browser address bar and can be manipulated without immediate validation errors.
  4. Check for existing input validation
    Review any reverse proxy, SAP Web Dispatcher, or application-level configurations that may handle URL parameter validation. Check the SAP Web Dispatcher configuration file (sapwebdisp.pfl) for URL filtering rules.
    Affected if No input validation filters are configured for the DTR endpoint and the component is publicly or semi-publicly accessible.

You are affected if your SAP NetWeaver Development Infrastructure version is exactly 7.30, 7.31, 7.40, or 7.50 AND the Design Time Repository web interface is accessible and processes URL parameters without sanitization.

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

Apply the relevant SAP security note/patch for CVE-2022-29618. Implement proper input validation and output encoding for all URL parameters to prevent script injection.

Recommended fix Moderate confidence
  1. Access the SAP Support Portal at launchpad.support.sap.com
  2. Search for Security Note related to CVE-2022-29618 or SAP NetWeaver Development Infrastructure XSS vulnerability
  3. Download and review the applicable SAP Security Note
  4. Apply the security patch or correction as detailed in the SAP Security Note
  5. Verify the patch has been applied successfully by checking the system version or through appropriate testing
  6. Clear browser cache and test the affected URL parameter to confirm the XSS vulnerability is remediated

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

Fix this in Netweaver Development Infrastructure 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-29618 — 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-29618 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