dbcve.org
NetweaverApplication · Sap

CVE-2023-33984

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

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
SAP NetWeaver (Design Time Repository) - version 7.50, returns an unfavorable content type for some versioned files, which could allow an authorized attacker to create a file with a malicious content and send a link to a victim in an email or instant message. Under certain circumstances, this could lead to Cross-Site Scripting vulnerability.

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

SAP NetWeaver Design Time Repository version 7.50 incorrectly sets content types for certain versioned files, allowing an authenticated attacker to embed malicious script content. When victims access these files via links, the improper content type causes the browser to execute the malicious code, resulting in reflected XSS.

MitigationApply the relevant SAP security patch for this vulnerability. Ensure the Design Time Repository properly sets Content-Type headers (e.g., text/plain or application/octet-stream) for all versioned files to prevent script execution.

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
NetweaverApplication
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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 version
    Check the installed SAP NetWeaver version by accessing the SAP System Information transaction (SM37 or similar) or by querying the SAP system via SAP MII version information. Verify the version matches 7.50.
    Affected if The installed SAP NetWeaver version is exactly 7.50 and includes the Design Time Repository component.
  2. Verify Design Time Repository is active
    Access the SAP NetWeaver Administrator or Configuration Wizard to confirm the Design Time Repository (DTR) component is installed and running. Check if DTR is accessible via HTTP/HTTPS endpoints.
    Affected if The Design Time Repository component is installed and active in the SAP NetWeaver 7.50 environment.
  3. Inspect DTR file serving configuration
    Review the DTR configuration settings related to content-type handling for versioned files. Check the SAP Web Dispatcher or ICM (Internet Communication Manager) settings if DTR is accessed via web.
    Affected if DTR is configured to serve versioned files without explicit content-type headers, or uses an unsafe content-type (such as text/html) for such files.
  4. Test DTR endpoint for content-type header behavior
    Send an HTTP request to a known versioned file URL within the DTR namespace and inspect the Content-Type header in the response. Compare against expected safe types (text/plain, application/octet-stream).
    Affected if The DTR serves versioned files with content-type headers that allow script execution (e.g., text/html) or omits proper content-type headers entirely.

A user is affected if they run SAP NetWeaver version 7.50 with the Design Time Repository component active and the DTR serves versioned files with unsafe or missing Content-Type headers that permit script execution in browsers.

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 patch for this vulnerability. Ensure the Design Time Repository properly sets Content-Type headers (e.g., text/plain or application/octet-stream) for all versioned files to prevent script execution.

Recommended fix Moderate confidence

SAP NetWeaver 7.50 with latest Support Package Stack (SPS) and applicable Security Note

  1. Check SAP Security Note for CVE-2023-33984 in SAP Support Portal (launchpad.support.sap.com)
  2. Apply the relevant SAP Note/patch for Design Time Repository in NetWeaver 7.50
  3. After patch deployment, verify the content type headers are correctly set for versioned files
  4. Test that versioned files are served with appropriate content-type (e.g., text/html should include X-Content-Type-Options: nosniff)
  5. Confirm the fix eliminates the XSS vector by validating that malicious content in files is not executed in browser context
Caveat Standard SAP patch deployment; test in QA system first to ensure no regression in DTR functionality

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

Fix this in Netweaver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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