# CVE-2017-15367: Bacula-web SQL Injection Vulnerabilities

> SQL injection in Bacula-web allows attackers to access the database and potentially escalate privileges on the server.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fv4m-5j2c-787r

## What is CVE-2017-15367?

CVE-2017-15367 is a critical SQL injection vulnerability in n/a, published on 7 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Bacula-web before 8.0.0-rc2 is affected by multiple SQL Injection vulnerabilities that could allow an attacker to access the Bacula database and, depending on configuration, escalate privileges on the server.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2017-15367?

2 open source packages ship an affected version, including bacula-web/bacula-web. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bacula-web/bacula-web` | Packagist | All versions | 8.0.0-rc2 |
| `bacula-web/bacula-web` | Packagist | All versions | 8.0.0-rc2 |

Products: Bacula Bacula-Web.

## How do I fix CVE-2017-15367?

Upgrade bacula-web/bacula-web to 8.0.0-rc2 or later.

## Is CVE-2017-15367 being exploited?

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

Public exploit code:

- Bacula-Web < 8.0.0-rc2 - SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2025-45346](https://insights.sbomify.com/CVE-2025-45346/): Bacula-web SQL Injection Vulnerability (high 8.1)
- [CVE-2014-8295](https://insights.sbomify.com/CVE-2014-8295/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15367 and fix it if it is affected.

What it is: CVE-2017-15367 is a critical SQL injection vulnerability in n/a, published on 7 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15367 in the wild and no public exploit code.

Affected packages and fixed versions:
- bacula-web/bacula-web (Packagist): affected all versions; fixed in 8.0.0-rc2
- bacula-web/bacula-web (Packagist): affected all versions; fixed in 8.0.0-rc2

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-2017-15367/ (Markdown: https://insights.sbomify.com/CVE-2017-15367/index.md)
```

## Sources

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

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