CVE-2022-22532
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 · uneditedIn SAP NetWeaver Application Server Java - versions KRNL64NUC 7.22, 7.22EXT, 7.49, KRNL64UC, 7.22, 7.22EXT, 7.49, 7.53, KERNEL 7.22, 7.49, 7.53, an unauthenticated attacker could submit a crafted HTTP server request which triggers improper shared memory buffer handling. This could allow the malicious payload to be executed and hence execute functions that could be impersonating the victim or even steal the victim's logon session.
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 · high confidenceA critical vulnerability in SAP NetWeaver Application Server Java allows unauthenticated remote attackers to execute arbitrary code via crafted HTTP requests that trigger improper shared memory buffer handling, enabling session hijacking and victim impersonation.
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.22= 7.49= 7.53= krnl64nuc_7.22= krnl64nuc_7.22ext= krnl64nuc_7.49= krnl64uc_7.22= krnl64uc_7.22ext= krnl64uc_7.49CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP NetWeaver AS Java kernel versionExecute SM51 transaction in SAP GUI or use SAP kernel version command: 'SAPCAR -tvf <kernel_archive>.SAR' to extract and read the version file. Alternatively, check the 'disp+work' executable version in the kernel directory.Affected if The kernel version matches 7.22, 7.49, or 7.53, or the kernel identifier matches krnl64nuc_7.22, krnl64nuc_7.22ext, krnl64nuc_7.49, krnl64uc_7.22, krnl64uc_7.22ext, or krnl64uc_7.49.
-
Confirm HTTP service is enabled on SAP AS JavaCheck SMICM transaction (Internet Communication Manager) or inspect icm/HTTP/logging_<sysnr> parameter in instance profile. Verify that HTTP port (typically 5<instance>00 or 8<instance>00) is listed as active.Affected if HTTP services are active and the SAP Java system is reachable via HTTP.
-
Verify Java stack is exposed to external networksReview network configuration: check ICF (Internet Communication Framework) services via SICF transaction, verify firewall rules allow external access to SAP HTTP ports, and inspect profile parameters icm/host_name_full for external bindings.Affected if The HTTP interface is accessible from untrusted networks or the internet.
-
Check for recent security-relevant changesReview SAP system logs in ST03N, SM37, and virus scan interface logs for unusual HTTP request patterns or authentication anomalies around the time frame of the CVE disclosure.Affected if Any suspicious HTTP activity is found or if patches have not been applied since February 2022.
Your environment is affected if the SAP NetWeaver AS Java kernel version matches any of the vulnerable versions (7.22, 7.49, 7.53, or their krnl64 variants) AND HTTP services are accessible, enabling unauthenticated attackers to exploit the shared memory buffer flaw via crafted HTTP 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.
dbcve · scopedApply SAP security patches for affected versions (KRNL64NUC 7.22/7.22EXT/7.49, KRNL64UC 7.22/7.22EXT/7.49/7.53, KERNEL 7.22/7.49/7.53) and restrict external HTTP access to SAP systems as an interim control.
- Navigate to the SAP Support Launchpad (launchpad.support.sap.com) and search for SAP Security Note related to CVE-2022-22532
- Identify the applicable SAP Security Note number (typically released by SAP to address this HTTP request smuggling vulnerability)
- Download and review the correction instructions from the SAP Security Note
- Apply the SAP Security Note using SAP Transport Management System (TMS) or manual correction as specified in the note
- After applying the patch, restart the SAP NetWeaver Application Server Java instance
- Verify the patch was applied successfully by checking the SAP system version and reviewing the installed security notes
- Test critical HTTP functionality to ensure the application server operates normally after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22532 — 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-2022-22532 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