dbcve.org
PmcApplication · Pilz

CVE-2019-9011

MEDIUM · 5.3 CVSS v3.1 Published 2022-12-26
Fix available
A fix is available. Upgrade to 3.5.17 or later.
See remediation →
62/100
Remediation priority · Elevated
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
In Pilz PMC programming tool 3.x before 3.5.17 (based on CODESYS Development System), an attacker can identify valid usernames.

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 Pilz PMC programming tool versions prior to 3.5.17 (built on CODESYS Development System) contains a username enumeration vulnerability. Attackers can distinguish between valid and invalid usernames by observing differential responses during authentication, allowing them to compile a list of valid user accounts.

MitigationUpdate Pilz PMC programming tool to version 3.5.17 or later. Until patched, enforce network segmentation and restrict access to the management interface to trusted networks only.

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
PmcApplication
Affected:>= 3.0.0, < 3.5.17

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Pilz PMC version
    Open Pilz PMC programming tool and navigate to Help > About, or check the installed software version in Windows Programs and Features
    Affected if Installed version is 3.0.0 through 3.5.16 (any version < 3.5.17)
  2. Determine network exposure
    Check if the PMC programming tool or its underlying CODESYS runtime is accessible over the network by reviewing firewall rules and listening ports (typically TCP ports 1217, 1743, 1744 for CODESYS)
    Affected if The authentication interface is reachable from untrusted networks
  3. Verify CODESYS Gateway access
    Inspect whether the CODESYS Gateway service (used by Pilz PMC) is configured to allow remote connections by examining the gateway configuration files or service settings
    Affected if Remote gateway connections are permitted and the service is network-accessible
  4. Test authentication response behavior
    If accessible, attempt authentication with both a valid and invalid username to the PMC/CODESYS login interface and compare the response times and error messages
    Affected if Different error messages or response patterns are returned for valid versus invalid usernames

You are affected if Pilz PMC version is below 3.5.17 and the authentication interface is network-accessible, allowing attackers to enumerate valid usernames through differential responses.

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.

dbcve · scoped
Upgrade available Upgrade to 3.5.17 or later
Fixed in 3.5.17
Interim mitigation

Update Pilz PMC programming tool to version 3.5.17 or later. Until patched, enforce network segmentation and restrict access to the management interface to trusted networks only.

Recommended fix High confidence

3.5.17

  1. 1. Identify the current version of Pilz PMC programming tool installed in your environment
  2. 2. Download Pilz PMC programming tool version 3.5.17 or later from the official vendor source (cert.vde.com or Pilz support channels)
  3. 3. Plan maintenance window - the upgrade may require stopping/starting the service or application
  4. 4. Perform a backup of current configuration and project files
  5. 5. Install the upgraded version (3.5.17 or later) following vendor installation procedures
  6. 6. Verify the upgrade was successful by checking the installed version
  7. 7. Test that legitimate usernames cannot be enumerated from external connections

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pmc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-9011 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-9011 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