CVE-2024-45044

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-41282 (ENISA EUVD)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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

CISA-ADP, in the CVE record, lists bareos versions 23.0.0 up to but not including 23.0.4, 22.0.0 up to but not including 22.1.6 and before 21.1.11 as affected. No release containing a fix is confirmed on record.

Bareos is open source software for backup, archiving, and recovery of data for operating systems. When a command ACL is in place and a user executes a command in bconsole using an abbreviation (i.e. "w" for "whoami") the ACL check did not apply to the full form (i.e. "whoami") but to the abbreviated form (i.e. "w"). If the command ACL is configured with negative ACL that should forbid using the "whoami" command, you could still use "w" or "who" as a command successfully. Fixes for the problem are shipped in Bareos versions 23.0.4, 22.1.6 and 21.1.11. If only positive command ACLs are used without any negation, the problem does not occur.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 10, 2024

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated May 22, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

Negative command ACLs can be circumvented by abbreviating commands · Advisory · bareos/bareos · GitHub

https://github.com/bareos/bareos/security/advisories/GHSA-jfww-q346-r2r8
Web page

Fix multiple ACL handling bugs by joergsteffens · Pull Request #1875 · bareos/bareos · GitHub

https://github.com/bareos/bareos/pull/1875
Web page

Merge pull request #1875 · bareos/bareos@2a02669 · GitHub

https://github.com/bareos/bareos/commit/2a026698b87d13bd1c6275726b5e826702f81dd5

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 225 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 128 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-45044?
CVE-2024-45044 is a high-severity vulnerability; its CVE record was published on September 10, 2024. Bareos is open source software for backup, archiving, and recovery of data for operating systems. When a command ACL is in place and a user executes a command in bconsole using an abbreviation (i.e. "w" for "whoami") the ACL check did not apply to the full form (i.e. "whoami") but to the…
When was the CVE record for CVE-2024-45044 published?
The CVE record for CVE-2024-45044 was published on September 10, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-45044 actively exploited?
CVE-2024-45044 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-45044?
CVE-2024-45044 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2024-45044?
No fix for CVE-2024-45044 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. CISA-ADP, in the CVE record, lists bareos versions 23.0.0 up to but not including 23.0.4, 22.0.0 up to but not including 22.1.6 and before 21.1.11 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-45044

Explore →

Is Your Infrastructure Affected by CVE-2024-45044?

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