CVE-2021-40499
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 · uneditedClient-side printing services SAP Cloud Print Manager and SAPSprint for SAP NetWeaver Application Server for ABAP - versions 7.70, 7.70 PI, 7.70 BYD, allow an attacker to inject code that can be executed by the application. An attacker could thereby control the behavior 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 confidenceA code injection vulnerability in SAP Cloud Print Manager and SAPSprint allows attackers to inject malicious code that gets executed by the application. This affects the client-side printing services for SAP NetWeaver AS ABAP versions 7.70, 7.70 PI, and 7.70 BYD, potentially giving attackers control over application behavior.
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.70= 7.70_pi= 7.70bydCVSS 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 ABAP versionCheck the SAP system version by accessing SAP transaction SM51 or using the SAP NetWeaver Administrator. Look for version 7.70, 7.70 PI, or 7.70 BYD specifically.Affected if The installed version matches exactly 7.70, 7.70_pi, or 7.70byd from the affected versions list.
-
Determine if SAPSprint service is runningOn the SAP host, check for the SAPSprint process or service. On Windows, view services via services.msc; on Unix, check for sapcpe or sprint processes. In SAP, use transaction SPRO_ADMIN or check print spool configuration.Affected if SAPSprint service is installed and active on the system.
-
Determine if SAP Cloud Print Manager is in useCheck if SAP Cloud Print Manager (CPM) components are installed. Review SAP print infrastructure configuration via transaction SP01 or SP02 for print spool administration, and verify if cloud print manager connectors are configured.Affected if SAP Cloud Print Manager is deployed or configured in the environment.
-
Inspect print job submission configurationReview print job submissions via SAP transaction SP01 (Output Controller) or SP02 (Spool Requests). Check for any custom print parameters, external commands, or script-based print outputs that could accept injected code.Affected if Print jobs can accept external inputs, custom scripts, or dynamic parameters without validation.
A system is affected if it runs SAP NetWeaver AS ABAP version 7.70, 7.70 PI, or 7.70 BYD AND has SAPSprint or SAP Cloud Print Manager services enabled and accessible.
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 this vulnerability. Until patched, restrict network access to printing services and implement input validation controls on print job submissions.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-40499 — 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-2021-40499 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