CVE-2016-2055
UnknownEPSS 17.85%
Last modified
CVE-2016-2055 is a vulnerability of currently unknown severity. xymond/xymond.c in xymond in Xymon 4.1.x, 4.2.x, and 4.3.x before 4.3.25 allow remote attackers to read arbitrary files in the configuration directory via a "config" command.. EPSS estimates a 17.85% chance of exploitation in the next 30 days.
Description
xymond/xymond.c in xymond in Xymon 4.1.x, 4.2.x, and 4.3.x before 4.3.25 allow remote attackers to read arbitrary files in the configuration directory via a "config" command.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Xymon | Xymon | 4.1.0 | — |
| Xymon | Xymon | 4.1.1 | — |
| Xymon | Xymon | 4.1.2 | — |
| Xymon | Xymon | 4.2 | Alfa |
| Xymon | Xymon | 4.2.0 | — |
| Xymon | Xymon | 4.2.2 | — |
| Xymon | Xymon | 4.2.3 | — |
| Xymon | Xymon | 4.3.0 | — |
| Xymon | Xymon | 4.3.1 | — |
| Xymon | Xymon | 4.3.2 | — |
| Xymon | Xymon | 4.3.3 | — |
| Xymon | Xymon | 4.3.4 | — |
| Xymon | Xymon | 4.3.5 | — |
| Xymon | Xymon | 4.3.6 | — |
| Xymon | Xymon | 4.3.7 | — |
| Xymon | Xymon | 4.3.8 | — |
| Xymon | Xymon | 4.3.9 | — |
| Xymon | Xymon | 4.3.10 | — |
| Xymon | Xymon | 4.3.11 | — |
| Xymon | Xymon | 4.3.12 | — |
| Xymon | Xymon | 4.3.13 | — |
| Xymon | Xymon | 4.3.14 | — |
| Xymon | Xymon | 4.3.15 | — |
| Xymon | Xymon | 4.3.16 | — |
| Xymon | Xymon | 4.3.17 | — |
| Xymon | Xymon | 4.3.18 | — |
| Xymon | Xymon | 4.3.19 | — |
| Xymon | Xymon | 4.3.20 | — |
| Xymon | Xymon | 4.3.21 | — |
| Xymon | Xymon | 4.3.22 | — |
| Xymon | Xymon | 4.3.23 | — |
| Xymon | Xymon | 4.3.24 | — |
| Debian | Debian Linux | 8.0 | — |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-2055?
xymond/xymond.c in xymond in Xymon 4.1.x, 4.2.x, and 4.3.x before 4.3.25 allow remote attackers to read arbitrary files in the configuration directory via a "config" command.
How severe is CVE-2016-2055?
Severity scoring for CVE-2016-2055 is pending analysis. The EPSS model estimates a 17.85% probability of exploitation in the next 30 days.
How do I fix CVE-2016-2055?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2016-2055?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST