CVE-2020-8006
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 · uneditedThe server in Circontrol Raption through 5.11.2 has a pre-authentication stack-based buffer overflow that can be exploited to gain run-time control of the device as root. The ocpp1.5 and pwrstudio binaries on the charging station do not use a number of common exploitation mitigations. In particular, there are no stack canaries and they do not use the Position Independent Executable (PIE) format.
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 confidenceStack-based buffer overflow in Circontrol Raption charging station server (versions through 5.11.2) that is exploitable pre-authentication, allowing attackers to gain root-level code execution. The vulnerable ocpp1.5 and pwrstudio binaries lack common exploit mitigations including stack canaries and Position Independent Executable (PIE) support.
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<= 5.11.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Raption server processesRun 'ps aux' or check running services for ocpp1.5, pwrstudio, or raption-related processesAffected if Any of these processes are running and correspond to Circontrol Raption software
-
Determine installed software versionCheck the version of the Raption server software via 'dpkg -l', 'rpm -qi', or look for version files in the installation directory (often /opt/circontrol or similar)Affected if Installed version is 5.11.2 or lower, or if version cannot be determined but the software is present
-
Locate vulnerable binariesSearch for ocpp1.5 and pwrstudio executable files using 'find / -name ocpp1.5' or 'find / -name pwrstudio'Affected if These binaries exist on the system and belong to Circontrol Raption version <= 5.11.2
-
Check binary exploit mitigations (optional)Use 'readelf -l <binary>' to check for PIE (flags include DYNAMIC) and 'readelf -s <binary>' to search for stack canary symbols; or use 'checksec --file=<binary>' if availableAffected if Binaries lack PIE (no DYNAMIC section flag) and lack stack canary symbols (no __stack_chk_fail symbols)
-
Assess network exposureRun 'netstat -tlnp' or 'ss -tlnp' to check if the Raption service ports (typically 8080, 8443, or SOAP ports) are listening on interfaces accessible from untrusted networksAffected if The service is bound to 0.0.0.0 or an exposed network interface without proper firewall restrictions
The environment is affected if Circontrol Raption Server version 5.11.2 or lower is installed with ocpp1.5 or pwrstudio binaries running and exposed to network access.
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 vendor-provided patch/update to Raption firmware/software to version beyond 5.11.2, which should include recompiled binaries with stack canaries and PIE enabled; until then, network-segment charging stations and restrict access to management interfaces.
- Consultation8.0 h
- Implementation4.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8006 — 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-8006 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