CVE-2021-27608
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 · uneditedAn unquoted service path in SAPSetup, version - 9.0, could lead to privilege escalation during the installation process that is performed when an executable file is registered. This could further lead to complete compromise of confidentiality, Integrity and 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 · high confidenceSAPSetup version 9.0 contains an unquoted service path vulnerability where the Windows service executable path contains spaces without quotation marks. During service installation, Windows searches for executables in path directories before the intended executable, allowing an attacker with local code execution to place a malicious binary in an intermediate directory that gets executed with elevated (SYSTEM) privileges, achieving privilege escalation.
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= 9.0CVSS 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
- Local
- Complexity
- High
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/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.
-
Verify SAPSetup version 9.0 is installedCheck the installed version by reviewing the program in Windows Programs and Features, or query the Windows Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named SAPSetup and confirm the Version value equals 9.0Affected if SAPSetup version 9.0 is present on the system
-
Locate the SAPSetup Windows serviceOpen Command Prompt as an administrator and run: sc queryex type= service state= all | findstr /i "SAPSetup" to enumerate services containing SAPSetup in the nameAffected if A Windows service with SAPSetup in its display name or service name exists
-
Inspect the service binary path for spacesRun: sc qc <service_name> (replace <service_name> with the discovered service name) and examine the BINARY_PATH_NAME field for spaces in the path that are not enclosed in quotation marksAffected if The BINARY_PATH_NAME contains spaces and is NOT wrapped in double quotation marks (e.g., C:\Program Files\SAP\Setup\bin\service.exe instead of "C:\Program Files\SAP\Setup\bin\service.exe")
-
Verify intermediate path directories existIf the service path is unquoted, parse each directory in the path (e.g., for C:\Program Files\SAP\Setup\bin\service.exe, check if C:\Program Files\ and C:\Program Files\SAP\ are writable by checking ACL permissions with icaclsAffected if Any directory in the path before the executable is writable by a low-privilege user, allowing them to place a malicious executable there
A user is affected if SAPSetup version 9.0 is installed, a related Windows service exists, and that service's binary path contains unquoted spaces with writable intermediate directories.
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 dataModify the service configuration to enclose the executable path in quotes, ensuring the full path to the service executable is properly quoted. Apply the vendor patch for SAPSetup when available and re-scan after changes.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27608 — 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-27608 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