CVE-2013-6359 json
Munin::Master::Node in Munin before 2.0.18 allows remote attackers to cause a denial of service (abort data collection for node) via a plug…
published 12y ago modified 4mo ago also EUVD-2013-6184
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
Munin::Master::Node in Munin before 2.0.18 allows remote attackers to cause a denial of service (abort data collection for node) via a plugin that uses "multigraph" as a multigraph service name.
Patch / fix
- munin Debian 14, Debian 13, Debian 12 2.0.18-1
debian advisories DEBIAN-CVE-2013-6359
- munin openSUSE Tumbleweed 2.0.25-4.10
opensuse advisories openSUSE-SU-2024:10330-1
Is CVE-2013-6359 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-6359 updated cvss 3.3
munin: two denial of service flaws fixed in 2.0.18
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.85% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
munin-monitoring.org
/ticket/1397
patch
-
debian.org
/security/2013/dsa-2815
vendor-advisory
-
ubuntu.com
/usn/USN-2090-1
vendor-advisory
- github.com /munin-monitoring/munin/blob/2.0.18/ChangeLog
Sources
- CVE List CVE-2013-6359
- NVD CVE-2013-6359
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.