# CVE-2018-25099: Weak cryptography in n/a

> The Perl CryptX module fails to verify authentication tags in GCM and ChaCha20-Poly1305 decryption, allowing attackers to bypass integrity checks.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 18 Mar 2024
- **Updated:** 14 Mar 2025
- **Also known as:** DEBIAN-CVE-2018-25099, GHSA-c39g-93pm-r85m, UBUNTU-CVE-2018-25099, openSUSE-SU-2024:0112-1, openSUSE-SU-2024:13866-1

## What is CVE-2018-25099?

CVE-2018-25099 is a critical vulnerability in n/a, published on 18 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the CryptX module before 0.062 for Perl, gcm_decrypt_verify() and chacha20poly1305_decrypt_verify() do not verify the tag.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-CryptX` | SUSE:Package Hub 15 SP5 | All versions | 0.80.0-bp155.2.3.1 |
| `perl-CryptX` | openSUSE:Leap 15.5 | All versions | 0.80.0-bp155.2.3.1 |
| `perl-CryptX` | openSUSE:Tumbleweed | All versions | 0.80.0-3.1 |

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

Upgrade to a fixed version.

## Is CVE-2018-25099 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25099 is a critical vulnerability in n/a, published on 18 Mar 2024. 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-25099 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-25099/ (Markdown: https://insights.sbomify.com/CVE-2018-25099/index.md)
```

## Sources

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

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