dbcve.org
CommoncryptolibApplication · Sap

CVE-2023-40308

HIGH · 7.5 CVSS v3.1 Published 2023-09-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
SAP CommonCryptoLib allows an unauthenticated attacker to craft a request, which when submitted to an open port causes a memory corruption error in a library which in turn causes the target component to crash making it unavailable. There is no ability to view or modify any information.

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 CommonCryptoLib contains a memory corruption vulnerability that can be triggered by unauthenticated crafted requests submitted to an open port. This causes the affected component to crash due to memory corruption, resulting in denial of service. The attacker has no capability to view or modify data.

MitigationRestrict network access to affected ports using firewalls or network segmentation. Monitor for availability issues on systems using SAP CommonCryptoLib. Apply SAP security patches when available.

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
CommoncryptolibApplication
Affected:= 8.0.0
Content ServerApplication
Affected:= 6.50= 7.53= 7.54
Extended Application Services And RuntimeApplication
Affected:= 1.0
Hana DatabaseDatabase / datastore
Affected:= 2.0
Host AgentApplication
Affected:= 722
Netweaver Application Server AbapApplication
Affected:= 7.22ext= kernel_7.22= kernel_7.53= kernel_7.54= kernel_7.77= kernel_7.85= kernel_7.89= kernel_7.91= kernel_7.92= kernel_7.93= kernel_8.04= kernel64nuc_7.22
Netweaver Application Server JavaApplication
Affected:= kernel_7.22= kernel_7.53= kernel_7.54= kernel_7.77= kernel_7.85= kernel_7.89= kernel_7.91= kernel_7.92= kernel_7.93= kernel_8.04= kernel64nuc_7.22= kernel64nuc_7.22ext
SapssoextApplication
Affected:= 17.0

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Identify installed SAP CommonCryptoLib version
    Locate the SAP CommonCryptoLib library on the system and query its version information. Common locations include the SAP installation directory under /cryptolib or similar paths. Use SAP management tools or check file properties to determine if version 8.0.0 is present.
    Affected if SAP CommonCryptoLib version 8.0.0 is installed on the system
  2. Identify installed SAP products
    Use SAP management tools such as SAPINST, SAPLM, or system inventory tools to enumerate installed SAP components. Check for the presence of SAP Content Server, SAP Extended Application Services and Runtime, SAP HANA Database, SAP Host Agent, SAP NetWeaver Application Server (ABAP or Java), or SAPSSOEXT.
    Affected if Any of the following products are installed: SAP Content Server 6.50/7.53/7.54, SAP EASR 1.0, SAP HANA DB 2.0, SAP Host Agent 722, SAP NetWeaver AS ABAP (kernel_7.22ext, kernel_7.22, kernel_7.53, kernel_7.54, kernel_7.77, kernel_7.85, kernel_7.89, kernel_7.91, kernel_7.92, kernel_7.93, kernel_8.04,
  3. Check network exposure of SAP services
    Review firewall rules, network configurations, and exposed ports to determine if SAP services using CommonCryptoLib are accessible from untrusted networks. Use netstat, ss, or network scanning tools to identify listening ports associated with SAP components.
    Affected if SAP services using CommonCryptoLib are exposed on open network ports accessible to unauthenticated attackers
  4. Verify affected kernel versions in NetWeaver environments
    For SAP NetWeaver ABAP or Java installations, query the kernel version using SAP transaction codes such as SM51 or via SAP management interfaces. Compare the kernel version strings against the listed affected versions.
    Affected if The NetWeaver kernel version matches any of the affected versions: kernel_7.22, kernel_7.53, kernel_7.54, kernel_7.77, kernel_7.85, kernel_7.89, kernel_7.91, kernel_7.92, kernel_7.93, kernel_8.04, kernel64nuc_7.22, kernel_7.22ext, or kernel64nuc_7.22ext
  5. Monitor for service availability issues
    Review system logs, SAP logs, and monitoring systems for signs of unexpected service crashes, memory corruption errors, or denial of service conditions that may indicate exploitation attempts.
    Affected if SAP services using CommonCryptoLib are experiencing unexplained crashes or memory corruption errors

A system is affected if it has SAP CommonCryptoLib version 8.0.0 installed, or runs any of the affected SAP products with network-accessible services using this component.

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

Restrict network access to affected ports using firewalls or network segmentation. Monitor for availability issues on systems using SAP CommonCryptoLib. Apply SAP security patches when available.

Fix this in Commoncryptolib 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-2023-40308 — 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-40308 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