CVE-2020-6364
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 Solution Manager and SAP Focused Run (update provided in WILY_INTRO_ENTERPRISE 9.7, 10.1, 10.5, 10.7), allows an attacker to modify a cookie in a way that OS commands can be executed and potentially gain control over the host running the CA Introscope Enterprise Manager,leading to Code Injection. With this, the attacker is able to read and modify all system files and also impact system 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 confidenceThis is a code injection vulnerability in SAP Solution Manager and SAP Focused Run (CA Introscope Enterprise Manager) where an attacker can modify a cookie to inject and execute OS commands. The vulnerability has a CVSS 10 score due to the ability to gain full control of the host, read/modify all system files, and impact system 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= 9.7= 10.1= 10.5= 10.7CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if Introscope Enterprise Manager is installedCheck for the presence of Introscope Enterprise Manager processes or installed directories. Look for processes named 'Introscope' or 'EnterpriseManager' or directories containing 'wily' or 'introscope' in the installation path.Affected if Introscope Enterprise Manager is present on the system
-
Determine the installed Introscope versionLocate the version file or check the product version through the Introscope Enterprise Manager configuration files or startup scripts. Common locations include the 'introscope' installation directory or check the product version via the management interface if accessible.Affected if The installed version is exactly 9.7, 10.1, 10.5, or 10.7
-
Verify network accessibility of the Enterprise ManagerCheck if the Introscope Enterprise Manager web interface or API is exposed to the network. Review firewall rules, network configurations, and listen addresses in the Introscope configuration files.Affected if The Enterprise Manager is accessible from untrusted networks (the vulnerability is exploitable remotely via cookie injection)
-
Inspect cookie handling configurationReview the Introscope Enterprise Manager configuration files for cookie processing settings. Look for any custom cookie handlers or validation configurations in the relevant config files within the Introscope directory.Affected if Custom or permissive cookie handling is configured (the vulnerability allows injection through cookie modification)
A system is affected if it runs Introscope Enterprise Manager version 9.7, 10.1, 10.5, or 10.7 and the service is network-accessible, since the flaw allows arbitrary OS command execution via crafted cookie values.
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 the provided update for WILY_INTRO_ENTERPRISE versions 9.7, 10.1, 10.5, or 10.7. If immediate patching is not possible, restrict network access to the Introscope Enterprise Manager and implement strict input validation on cookie handling as compensating controls.
- 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-2020-6364 — 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-2020-6364 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