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.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-2049examples/consumer/common.php in JanRain PHP OpenID library (…
- CVE-2016-2050The get_abbrev_array_info function in libdwarf-20151114 allo…6.5
- CVE-2016-2051Multiple unspecified vulnerabilities in Google V8 before 4.8…
- CVE-2016-2052Multiple unspecified vulnerabilities in HarfBuzz before 1.0.…
- CVE-2016-2053The asn1_ber_decoder function in lib/asn1_decoder.c in the L…
- CVE-2016-2054Multiple buffer overflows in xymond/xymond.c in xymond in Xy…
- CVE-2016-2056xymond in Xymon 4.1.x, 4.2.x, and 4.3.x before 4.3.25 allow …
- CVE-2016-2057lib/xymond_ipc.c in Xymon 4.1.x, 4.2.x, and 4.3.x before 4.3…
- CVE-2016-2058Multiple cross-site scripting (XSS) vulnerabilities in Xymon…
- CVE-2016-2059The msm_ipc_router_bind_control_port function in net/ipc_rou…7
- CVE-2016-2060server/TetherController.cpp in the tethering controller in n…
- CVE-2016-2061Integer signedness error in the MSM V4L2 video driver for th…7.8
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