# CVE-2025-40919: Authen::DigestMD5 versions 0.01 through 0.04 for Perl generate the cnonce insecurely


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 16 Jul 2025
- **Updated:** 16 Jul 2025
- **Also known as:** GHSA-42f3-32q6-x99r

## What is CVE-2025-40919?

CVE-2025-40919 is a medium-severity vulnerability in SALVA Authen::DigestMD5, published on 16 Jul 2025. 

### Official description

Authen::DigestMD5 versions 0.01 through 0.02 for Perl generate the cnonce insecurely.

The cnonce (client nonce) is generated from an MD5 hash of the PID, the epoch time and the built-in rand function. The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand function is unsuitable for cryptographic usage.

According to RFC 2831, "The cnonce-value is an opaque quoted string value provided by the client and used by both client and server to avoid chosen plaintext attacks, and to provide mutual authentication. The security of the implementation depends on a good choice. It is RECOMMENDED that it contain at least 64 bits of entropy."

Weakness: CWE-340 (Generation of Predictable Numbers or Identifiers), CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2025-40919?


## How do I fix CVE-2025-40919?

No fix has been published for CVE-2025-40919 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-40919 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40919 and fix it if it is affected.

What it is: CVE-2025-40919 is a medium-severity vulnerability in SALVA Authen::DigestMD5, published on 16 Jul 2025. 
Exploitation: There is no known exploitation of CVE-2025-40919 in the wild and no public exploit code.

Affected product: SALVA Authen::DigestMD5. 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-2025-40919/ (Markdown: https://insights.sbomify.com/CVE-2025-40919/index.md)
```

## Sources

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

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