CVE-2019-12105

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 2.3%, top 19% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In Supervisor through 4.0.2, an unauthenticated user can read log files or restart a service. Note: The maintainer responded that the affected component, inet_http_server, is not enabled by default but if the user enables it and does not set a password, Supervisor logs a warning message. The maintainer indicated the ability to run an open server will not be removed but an additional warning was added to the documentation

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
53(Track)
EG Risk 53/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation2% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
82%
KEV
Not listed

Published

September 10, 2019

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Sep 8, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

[CVE-2019-12105] Unauthenticated user can read log files or restart a service · Issue #1245 · Supervisor/supervisor · GitHub

https://github.com/Supervisor/supervisor/issues/1245
github_commit

commit 4e334d9cf2a1 (Supervisor/supervisor)

Fix landed in Supervisor/supervisor commit 4e334d9cf2a1 — awaiting tagged release

https://github.com/Supervisor/supervisor/commit/4e334d9cf2a1daff685893e35e72398437df3dcb
generic

Configuration File — Supervisor 4.3.0 documentation

http://supervisord.org/configuration.html#inet-http-server-section-settings

Affected Packages

(18 across 18 ecosystems)
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Alpine:v3.13(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Alpine:v3.14(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
supervisor—4.1.0-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
supervisor4.2.2-2 ... 4.3.0-2 (9 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
supervisor4.2.5-1 ... 4.3.0-2 (6 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
supervisor4.2.5-3, 4.3.0-1, 4.3.0-2——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
supervisor4.2.5-3, 4.3.0-1, 4.3.0-2——
PyPI(1)
PackageVulnerable rangeFixed inDependents
supervisora3 ... 4.0.2 (42 versions)4.0.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 145 total refreshes for this CVE.

  1. 2026-09-18 19:22 UTCEPSS rescore
  2. 2026-09-17 19:22 UTCEPSS rescore
  3. 2026-09-16 14:04 UTCEPSS rescore
  4. 2026-09-15 03:05 UTCEPSS rescore
  5. 2026-09-13 16:42 UTCEPSS rescore
  6. 2026-09-12 14:56 UTCEPSS rescore
  7. 2026-09-11 14:48 UTCEPSS rescore
  8. 2026-09-08 21:55 UTCEPSS rescore
  9. 2026-09-08 04:22 UTCOSV refresh
  10. 2026-09-07 15:57 UTCEPSS rescore
  11. 2026-09-06 13:44 UTCEPSS rescore
  12. 2026-09-05 15:24 UTCEPSS rescore
  13. 2026-09-04 13:56 UTCEPSS rescore
  14. 2026-09-04 05:02 UTCEPSS rescore
  15. 2026-09-02 14:07 UTCEPSS rescore
  16. 2026-09-01 03:32 UTCEPSS rescore
  17. 2026-08-30 19:13 UTCEPSS rescore
  18. 2026-08-30 01:18 UTCEPSS rescore
  19. 2026-08-28 21:36 UTCEPSS rescore
  20. 2026-08-27 14:21 UTCEPSS rescore
  21. 2026-08-26 14:42 UTCEPSS rescore
  22. 2026-08-25 13:45 UTCEPSS rescore
  23. 2026-08-21 23:45 UTCEPSS rescore
  24. 2026-08-21 14:44 UTCOSV refresh
  25. 2026-08-20 22:51 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:00 UTCEPSS rescore
  2. 2026-08-18 13:44 UTCEPSS rescore
  3. 2026-08-17 13:43 UTCEPSS rescore
  4. 2026-08-16 14:52 UTCEPSS rescore
  5. 2026-08-16 02:10 UTCEPSS rescore
  6. 2026-08-15 01:26 UTCEPSS rescore
  7. 2026-08-13 21:56 UTCEPSS rescore
  8. 2026-08-12 13:47 UTCEPSS rescore
  9. 2026-08-09 13:43 UTCEPSS rescore
  10. 2026-08-08 16:33 UTCEPSS rescore
  11. 2026-08-07 16:23 UTCEPSS rescore
  12. 2026-08-06 13:43 UTCEPSS rescore
  13. 2026-08-06 00:54 UTCOSV refresh
  14. 2026-08-05 19:13 UTCEPSS rescore
  15. 2026-08-04 15:05 UTCEPSS rescore
  16. 2026-08-04 10:33 UTCEPSS rescore
  17. 2026-08-03 10:31 UTCEPSS rescore
  18. 2026-08-02 02:23 UTCEPSS rescore
  19. 2026-08-01 04:12 UTCEPSS rescore
  20. 2026-07-30 16:24 UTCEPSS rescore
  21. 2026-07-30 01:27 UTCEPSS rescore
  22. 2026-07-28 15:32 UTCEPSS rescore
  23. 2026-07-26 14:51 UTCEPSS rescore
  24. 2026-07-25 14:14 UTCEPSS rescore
  25. 2026-07-24 14:14 UTCEPSS rescore
  26. 2026-07-24 14:14 UTCEPSS rescore
  27. 2026-07-23 14:15 UTCEPSS rescore
  28. 2026-07-23 01:39 UTCEG score recompute
  29. 2026-07-22 22:19 UTCEG score recompute
  30. 2026-07-22 14:05 UTCEPSS rescore
  31. 2026-07-21 15:22 UTCEPSS rescore
  32. 2026-07-21 15:22 UTCEPSS rescore
  33. 2026-07-20 17:04 UTCEPSS rescore
  34. 2026-07-20 06:34 UTCOSV refresh
  35. 2026-07-19 14:28 UTCEPSS rescore
  36. 2026-07-19 14:28 UTCEPSS rescore
  37. 2026-07-19 02:26 UTCEPSS rescore
  38. 2026-07-19 02:26 UTCEPSS rescore
  39. 2026-07-18 10:01 UTCEPSS rescore
  40. 2026-07-16 16:59 UTCEPSS rescore
  41. 2026-07-16 16:59 UTCEPSS rescore
  42. 2026-07-15 16:55 UTCEPSS rescore
  43. 2026-07-13 22:27 UTCEPSS rescore
  44. 2026-07-13 06:10 UTCEPSS rescore
  45. 2026-07-13 06:10 UTCEPSS rescore
  46. 2026-07-12 05:43 UTCEPSS rescore
  47. 2026-07-11 08:24 UTCEPSS rescore
  48. 2026-07-09 19:06 UTCEPSS rescore
  49. 2026-07-08 15:11 UTCEPSS rescore
  50. 2026-07-07 13:42 UTCEPSS rescore
  51. 2026-07-06 16:25 UTCEPSS rescore
  52. 2026-07-06 02:20 UTCEPSS rescore
  53. 2026-07-05 02:27 UTCEPSS rescore
  54. 2026-07-04 06:28 UTCEPSS rescore
  55. 2026-07-04 06:28 UTCEPSS rescore
  56. 2026-07-02 23:35 UTCOSV refresh
  57. 2026-07-02 16:56 UTCEPSS rescore
  58. 2026-07-01 15:03 UTCEPSS rescore
  59. 2026-07-01 15:03 UTCEPSS rescore
  60. 2026-06-30 23:20 UTCEPSS rescore
  61. 2026-06-30 23:20 UTCEPSS rescore
  62. 2026-06-29 14:03 UTCEPSS rescore
  63. 2026-06-28 14:04 UTCEPSS rescore
  64. 2026-06-28 04:54 UTCEPSS rescore
  65. 2026-06-28 04:53 UTCEPSS rescore
  66. 2026-06-27 03:06 UTCEPSS rescore
  67. 2026-06-27 03:06 UTCEPSS rescore
  68. 2026-06-25 13:47 UTCEPSS rescore
  69. 2026-06-25 13:47 UTCEPSS rescore
  70. 2026-06-24 14:03 UTCEPSS rescore
  71. 2026-06-24 14:02 UTCEPSS rescore
  72. 2026-06-23 21:30 UTCEPSS rescore
  73. 2026-06-23 21:30 UTCEPSS rescore
  74. 2026-06-21 14:54 UTCEPSS rescore
  75. 2026-06-21 14:54 UTCEPSS rescore

Frequently asked(5)

What is CVE-2019-12105?
CVE-2019-12105 is a high vulnerability published on September 10, 2019. In Supervisor through 4.0.2, an unauthenticated user can read log files or restart a service. Note: The maintainer responded that the affected component, inethttpserver, is not enabled by default but if the user enables it and does not set a password, Supervisor logs a warning message. The…
When was CVE-2019-12105 disclosed?
CVE-2019-12105 was first published in the National Vulnerability Database on September 10, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-12105 actively exploited?
CVE-2019-12105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 17.6% of all scored CVEs.
What is the CVSS score of CVE-2019-12105?
CVE-2019-12105 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2019-12105?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-12105, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-12105

Explore →

Is Your Infrastructure Affected by CVE-2019-12105?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs