# CVE-2017-12618: Denial of service in Apache Portable Runtime

> A local attacker with write access to SDBM database files can cause a denial of service via out-of-bounds read in APR-util.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-12618, DLA-1163-1, GHSA-cxw3-v6f8-2cpm, MGASA-2017-0427, SUSE-SU-2017:3278-1, SUSE-SU-2018:0307-1, UBUNTU-CVE-2017-12618, USN-5737-1, openSUSE-SU-2024:10629-1

## What is CVE-2017-12618?

CVE-2017-12618 is a medium-severity denial of service vulnerability in Apache Portable Runtime, published on 24 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Apache Portable Runtime Utility (APR-util) 1.6.0 and prior fail to validate the integrity of SDBM database files used by apr_sdbm*() functions, resulting in a possible out of bound read access. A local user with write access to the database can make a program or process using these functions crash, and cause a denial of service.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libapr-util1` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 1.3.4-12.22.23.3.2 |
| `libapr-util1` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 1.5.3-2.3.1 |
| `libapr-util1` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 1.5.3-2.3.1 |
| `libapr-util1` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 1.5.3-2.3.1 |
| `libapr-util1` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 1.3.4-12.22.23.3.2 |
| `libapr-util1` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.5.3-2.3.1 |
| `libapr-util1` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 1.5.3-2.3.1 |
| `libapr-util1` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 1.3.4-12.22.23.3.2 |
| `libapr-util1` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 1.5.3-2.3.1 |
| `libapr-util1` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 1.5.3-2.3.1 |
| `libapr-util1` | SUSE:Studio Onsite 1.3 | All versions | 1.3.4-12.22.23.3.2 |
| `apr-util` | openSUSE:Tumbleweed | All versions | 1.6.1-7.8 |

Products: Apache Portable Runtime Utility.

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

Upgrade to a fixed version.

## Is CVE-2017-12618 being exploited?

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

## Other vulnerabilities in Apache Portable Runtime

- [CVE-2022-25147](https://insights.sbomify.com/CVE-2022-25147/): Apache Portable Runtime Utility (APR-util): out-of-bounds writes in the apr_base64 family of functions (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12618 is a medium-severity denial of service vulnerability in Apache Portable Runtime, published on 24 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12618 in the wild and no public exploit code.

Affected product: Apache Portable Runtime. 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-2017-12618/ (Markdown: https://insights.sbomify.com/CVE-2017-12618/index.md)
```

## Sources

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

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