Unauthenticated disclosure of valid usernames
Published Dec 26, 2022 · Updated Apr 14, 2025
Information disclosure in Pilz PMC programming tool 3.x before 3.5.17 allows remote attackers to identify valid usernames. Pilz has not published the affected authentication component or the operation that exposes whether a submitted username is valid. The interface is reachable without authentication over a network, and the disclosed account names can support targeted credential attacks.
Summary
What happened
Information disclosure in Pilz PMC programming tool 3.x before 3.5.17 allows remote attackers to identify valid usernames. Pilz has not published the affected authentication component or the operation that exposes whether a submitted username is valid. The interface is reachable without authentication over a network, and the disclosed account names can support targeted credential attacks.
The record
- CVE
- CVE-2019-9011
- Published
- Dec 26, 2022
- Updated
- Apr 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-668, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 26, 2022CVE publishedPublication date reported by the CVE source.
- Apr 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo