Pcoweb Card FirmwareOperating system · Carel

CVE-2019-9484

HIGH · 7.5 CVSS v3.0 Published 2019-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The Glen Dimplex Deutschland GmbH implementation of the Carel pCOWeb configuration tool allows remote attackers to obtain access via an HTTP session on port 10000, as demonstrated by reading the modem password (which is 1234), or reconfiguring "party mode" or "vacation mode."

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 confidence

The Carel pCOWeb configuration tool (implemented by Glen Dimplex Deutschland GmbH) exposes an unauthenticated HTTP interface on port 10000, allowing remote attackers to access sensitive configuration data including a hardcoded modem password (1234) and modify system settings such as party mode or vacation mode. This represents a critical authentication bypass or default credential vulnerability.

MitigationChange default credentials immediately, restrict network access to port 10000 via firewall rules or network segmentation, and disable remote HTTP management if not required.

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
Pcoweb Card FirmwareOperating system
Affected:all versions

CVSS 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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Carel pCOWeb service is running
    Scan your network for hosts responding on TCP port 10000, or check running services on known HVAC/building management systems for processes listening on port 10000
    Affected if A service is listening on TCP port 10000 on any system
  2. Verify HTTP interface accessibility
    Attempt an HTTP request to the suspected pCOWeb device on port 10000 (e.g., curl http://target:10000/) without providing any credentials
    Affected if The HTTP interface returns a response without requiring authentication
  3. Check for sensitive data exposure
    Inspect the HTTP response from port 10000 for sensitive configuration data, including modem password fields or system settings like party mode or vacation mode parameters
    Affected if The response contains configuration data, passwords, or system mode settings without having logged in
  4. Test default credential susceptibility
    If authentication is required, attempt to authenticate using the hardcoded password '1234' or check if the interface accepts any login without credential validation
    Affected if The default password 1234 grants access or no authentication is required for configuration changes
  5. Confirm product identity
    Examine HTTP response headers, HTML title, or favicon to confirm the service is Carel pCOWeb (look for 'pCOWeb' or Carel-related strings in the interface)
    Affected if The service on port 10000 is identified as Carel pCOWeb Card Firmware

Your environment is affected if a Carel pCOWeb service is accessible on port 10000 without authentication or with the default password 1234, allowing unauthorized access to sensitive configuration data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Change default credentials immediately, restrict network access to port 10000 via firewall rules or network segmentation, and disable remote HTTP management if not required.

Fix this in Pcoweb Card Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-9484 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-9484 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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