LiveActive security incident?Get immediate response
CVE Record

CVE-2020-8006: The server in Circontrol Raption through 5.11.2 has a pre-authentication stack-based buffer overflow that c...

The 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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-8006 affects Circontrol Raption charging stations through version 5.11.2. The issue is a memory-safety flaw reachable before authentication, and the CVE description says exploitation can give root-level control of the device. That makes it a serious operational risk for exposed EV charging infrastructure.

Executive priority

Prioritize remediation for internet-facing or third-party reachable chargers. Successful exploitation could give an attacker root control of affected devices, creating availability, safety, and operational disruption concerns. If exposure is only tightly segmented, urgency remains high but can be managed through controlled remediation.

Technical view

The CVE describes a pre-authentication stack-based buffer overflow in the Raption server. The ocpp1.5 and pwrstudio binaries reportedly lack stack canaries and PIE, reducing exploitation resistance. CVSS is 8.8 high; note the supplied vector lists PR:L, while the description says pre-authentication.

Likely exposure

Organizations operating Circontrol Raption chargers through 5.11.2 should assume exposure, especially where charger services are reachable from untrusted networks. The source bundle does not provide CPE data or a definitive vendor fix version.

Exploitation context

The supplied data does not show CISA KEV listing or confirmed active exploitation. A public Full Disclosure reference exists, so technical details may be publicly available. Do not treat this as only theoretical for exposed devices.

Researcher notes

Key evidence is the CVE description and Full Disclosure reference. The affected-products metadata is incomplete, and no patch instructions are included in the supplied bundle. Validate product versioning and remediation directly with Circontrol before asserting fixed releases.

Mitigation direction

  • Inventory Circontrol Raption chargers and firmware versions immediately.
  • Check Circontrol guidance for fixed firmware or vendor-supported remediation.
  • Remove charger management services from direct internet exposure.
  • Restrict access to trusted networks, VPNs, and required management hosts only.
  • Increase monitoring for crashes, restarts, and anomalous connections.

Validation and detection

  • Confirm whether any Raption device runs version 5.11.2 or earlier.
  • Map reachable charger services from internal and external network zones.
  • Review firewall rules for unnecessary inbound access to charger services.
  • Check device and network logs for unexpected crashes or connection spikes.
  • Document compensating controls where firmware remediation is not confirmed.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-121: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-8006 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2020-8006Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.