Openwsman is a systems-management implementation focused on WS-Management protocol support, with a narrowly scoped product footprint centered on the openwsman daemon itself. Observed vulnerabilities cluster around code-injection risks and memory-bounds issues, reflecting the parsing and dynamic-execution demands inherent to protocol handlers and scripting integration. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Openwsman over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2019-3833HIGH Openwsman, versions up to and including 2.6.9, are vulnerable to infinite loop in process_connection() when parsing specially crafted HTTP requests. A remote, unauthenticated attac | Mar 14, 2019 | 7.5 | 31 | NO | NO |
CVE-2019-3816HIGH Openwsman, versions up to and including 2.6.9, are vulnerable to arbitrary file disclosure because the working directory of openwsmand daemon was set to root directory. A remote, u | Mar 14, 2019 | 7.5 | 31 | NO | NO |
CVE-2008-2234HIGH Multiple buffer overflows in Openwsman 1.2.0 and 2.0.0 allow remote attackers to execute arbitrary code via a crafted "Authorization: Basic" HTTP header. | Aug 18, 2008 | 7.5 | 22 | NO | NO |
CVE-2008-2233HIGH The client in Openwsman 1.2.0 and 2.0.0, in unknown configurations, allows remote Openwsman servers to replay SSL sessions via unspecified vectors. | Aug 18, 2008 | 7.5 | 19 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Openwsman.
Media articles that mention a CVE ID that affects a product developed by Openwsman — matched by CVE ID, not by vendor name.