# CVE-2024-45044: Bareos's negative command ACLs can be circumvented by abbreviating commands

> Attackers can bypass negative command ACLs in Bareos by using command abbreviations, allowing execution of forbidden commands.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2024
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-jfww-q346-r2r8, UBUNTU-CVE-2024-45044

## What is CVE-2024-45044?

CVE-2024-45044 is a high-severity vulnerability in bareos, published on 10 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2024-45044?


## How do I fix CVE-2024-45044?

No fix has been published for CVE-2024-45044 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-45044 being exploited?

There is no known exploitation of CVE-2024-45044 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45044 and fix it if it is affected.

What it is: CVE-2024-45044 is a high-severity vulnerability in bareos, published on 10 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45044 in the wild and no public exploit code.

Affected product: bareos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-45044/ (Markdown: https://insights.sbomify.com/CVE-2024-45044/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45044
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45044
- OSV: https://osv.dev/vulnerability/CVE-2024-45044

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-45044/
Summaries are generated and may contain mistakes; the official description above is the record.