LiveActive security incident?Get immediate response
CVE Record

CVE-2020-18329: An issue was discovered in Rehau devices that use a pCOWeb card BIOS v6.27, BOOT v5.00, web version v2.2, a...

An issue was discovered in Rehau devices that use a pCOWeb card BIOS v6.27, BOOT v5.00, web version v2.2, allows attackers to gain full unauthenticated access to the configuration and service interface.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-18329 describes Rehau devices using a Carel pCOWeb card where unauthenticated users can access configuration and service interfaces. For executives, the concern is unauthorized visibility into device configuration over the network, especially if these interfaces are exposed beyond trusted operations networks.

Executive priority

Treat this as a high-priority exposure management issue for affected operational devices. Prioritize internet-exposed or remotely accessible systems first, because the CVE requires no authentication and affects sensitive configuration access.

Technical view

The CVE states affected Rehau devices use pCOWeb card BIOS v6.27, BOOT v5.00, and web version v2.2. The flaw allows full unauthenticated access to configuration and service interfaces. CVSS 3.1 is 7.5, network exploitable, low complexity, no privileges or user interaction, with high confidentiality impact.

Likely exposure

Exposure is most likely in environments running Rehau devices with the specified pCOWeb card versions. Risk increases where the web/service interface is reachable from the internet, shared corporate networks, vendor remote-access paths, or poorly segmented operational networks.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Public vulnerability references exist, and the CVE describes unauthenticated network access, but no source here proves exploitation in the wild.

Researcher notes

The record lacks standardized affected CPEs, a named patch, and confirmed exploitation evidence. Analysis should stay bounded to Rehau devices using the specified pCOWeb versions. Validate exposure by version and network reachability rather than assuming all Rehau or Carel deployments are affected.

Mitigation direction

  • Identify Rehau devices using the specified pCOWeb BIOS, BOOT, and web versions.
  • Remove public internet access to pCOWeb configuration and service interfaces.
  • Restrict access to trusted management networks or VPN-only paths.
  • Request vendor guidance from Rehau or Carel for supported firmware or configuration fixes.
  • Monitor device configuration changes and unexpected management-interface access.

Validation and detection

  • Inventory devices and record pCOWeb BIOS, BOOT, and web versions.
  • Confirm configuration and service interfaces are not reachable from untrusted networks.
  • Review external exposure data for reachable pCOWeb web interfaces.
  • Check device logs or management records for unknown access or configuration changes.
  • Document compensating controls where vendor fixes are unavailable.
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-281: 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-18329 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
7.5 (3.1)
Known Exploited
No
Published

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

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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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-281 · source CWE mapping

Improper Preservation of Permissions

Improper Preservation of Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.