CVE-2023-31405
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 · uneditedSAP NetWeaver AS for Java - versions ENGINEAPI 7.50, SERVERCORE 7.50, J2EE-APPS 7.50, allows an unauthenticated attacker to craft a request over the network which can result in unwarranted modifications to a system log without user interaction. There is no ability to view any information or any effect on availability.
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 confidenceThis is a log injection vulnerability in SAP NetWeaver AS for Java (version 7.50) that allows unauthenticated remote attackers to modify system logs via specially crafted network requests. The attack impacts system integrity by allowing log poisoning/tainting but does not affect confidentiality or availability.
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= 7.50CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP NetWeaver AS for Java installationLocate the SAP NetWeaver Java installation directory or use SAP transaction code SM51 to view running instances. In the SAP system, check the Java cluster and identify the AS Java component.Affected if The system has SAP NetWeaver Application Server for Java installed and running
-
Determine the installed Java AS versionExecute the SAP command 'jstart version' or access the SAP NetWeaver Administrator (NWA) at /nwa and navigate to 'System' > 'Information' > 'About SAP NetWeaver'. Alternatively, check the file 'sapcpe.jar' version in the /usr/sap/<SID>/SYS/exe/run directory.Affected if The version reported is exactly 7.50 (the vulnerable version)
-
Verify network-facing configurationUse SAP transaction code SMICM (ICM Monitor) to check if the Internet Communication Manager is active and exposed to network requests. Review the ICM ports configured under 'Goto' > 'Services' in SMICM.Affected if The ICM is active and listening on network ports (not localhost-only)
-
Confirm logging subsystem is enabledSAP NetWeaver Java logs are typically always enabled. Verify by accessing the Log Viewer in SAP NetWeaver Administrator (/nwa) under 'Troubleshooting' > 'Logs' > 'Log Viewer', or check that defaultTrace files exist in /usr/sap/<SID>/<instance>/j2ee/cluster/server0/log/Affected if Logging is enabled (default state in SAP NetWeaver Java)
The environment is affected if SAP NetWeaver AS for Java version 7.50 is installed and the ICM network listener is active, allowing external attackers to inject malicious content into system logs via crafted HTTP/HTTPS requests.
Generated from the published advisory. Verify against your own configuration.
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 dataApply SAP security patches for CVE-2023-31405 when available. Restrict network access to SAP NetWeaver Java systems to trusted sources only as a compensating control.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31405 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-31405 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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