CVE-2023-41366
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 · uneditedUnder certain condition SAP NetWeaver Application Server ABAP - versions KERNEL 722, KERNEL 7.53, KERNEL 7.77, KERNEL 7.85, KERNEL 7.89, KERNEL 7.54, KERNEL 7.91, KERNEL 7.92, KERNEL 7.93, KERNEL 7.94, KERNEL64UC 7.22, KERNEL64UC 7.22EXT, KERNEL64UC 7.53, KERNEL64NUC 7.22, KERNEL64NUC 7.22EXT, allows an unauthenticated attacker to access the unintended data due to the lack of restrictions applied which may lead to low impact in confidentiality and no impact on the integrity and availability 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 confidenceSAP NetWeaver Application Server ABAP contains a missing authorization control that allows unauthenticated attackers to access data they should not be able to view. The vulnerability affects multiple kernel versions and results from a lack of proper restrictions being applied under certain conditions.
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= 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_7.94= kernel64nuc_7.22= kernel64nuc_7.22extCVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SAP NetWeaver ABAP kernel versionDetermine the kernel version of your SAP NetWeaver Application Server ABAP installation. Use SAP transaction SM51 to display the kernel release, or check the kernel version via the SAPMMC or command line tools available in your environment.Affected if The installed kernel version matches one 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_7.94, kernel64nuc_7.22, or kernel64nuc_7.22ext
-
Verify if the system allows unauthenticated access to SAP servicesReview your network configuration to determine if SAP application servers and ports are accessible from unauthenticated or unauthorized network segments. Check firewall rules, network ACLs, and any SAP Gateway or Message Server exposures.Affected if SAP services are accessible from unauthorized network segments without proper network-level restrictions, allowing unauthenticated attackers to reach the affected components
-
Confirm the affected authorization scenario appliesSince this is a missing authorization control vulnerability, determine if your environment uses the specific ABAP functionality or transactions that lack proper authorization checks. This typically requires reviewing the specific data access paths mentioned in the security note.Affected if The system uses ABAP components or data access paths that are missing the proper authorization controls referenced in the security note for your kernel version
You are affected if your SAP NetWeaver ABAP kernel version matches one of the listed affected versions AND your system can be reached by unauthenticated attackers from unauthorized network segments.
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.
dbcve · scopedApply the relevant SAP security patches for the affected kernel versions. Until patches are available, implement network-level restrictions to limit exposure of the SAP services to unauthorized network segments.
Latest available kernel patch for your respective version (7.22 EXT, 7.53, 7.54, 7.77, 7.85, 7.89, 7.91, 7.92, 7.93, 7.94, KERNEL64UC, KERNEL64NUC) as specified in SAP Security Note 3266379 or successor
- Identify the current SAP NetWeaver ABAP kernel version using transaction SM51 or by checking the kernel patch level
- Review SAP Note 3266379 (or most recent related security note) for this CVE to obtain the specific kernel patch required
- Apply the latest available kernel patch for your respective kernel version (7.22, 7.53, 7.54, 7.77, or newer) that includes the security fix
- After kernel update, restart the SAP instance following standard SAP kernel upgrade procedures
- Verify the fix is applied by checking the kernel version again and confirming the security note is implemented
- Test critical ABAP transactions and RFC connections to ensure normal operation post-patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41366 — 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-41366 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