# CVE-2018-12088: Other in n/a

> An attacker controlling the backend can replay old metadata to temporarily hide or corrupt file contents in S3QL filesystems.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-12088, GHSA-49xr-rr65-3xpc, UBUNTU-CVE-2018-12088

## What is CVE-2018-12088?

CVE-2018-12088 is a high-severity vulnerability in n/a, published on 10 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

S3QL before 2.27 mishandles checksumming, and consequently allows replay attacks in which an attacker who controls the backend can present old versions of the filesystem metadata database as up-to-date, temporarily inject zero-valued bytes into files, or temporarily hide parts of files. This is related to the checksum_basic_mapping function.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-12088?

It affects 1 product.


Products: S3ql Project S3ql.

## How do I fix CVE-2018-12088?

Upgrade to a fixed version.

## Is CVE-2018-12088 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-0485](https://insights.sbomify.com/CVE-2014-0485/): Deserialization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12088 and fix it if it is affected.

What it is: CVE-2018-12088 is a high-severity vulnerability in n/a, published on 10 Jun 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-2018-12088 in the wild and no public exploit code.

Affected product: n/a. 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-2018-12088/ (Markdown: https://insights.sbomify.com/CVE-2018-12088/index.md)
```

## Sources

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

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