# CVE-2020-16155: Other in n/a

> The CPAN::Checksums Perl module fails to uniquely define signed data, potentially compromising data integrity verification.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-16155, GHSA-7c2g-m3j2-jrgq, UBUNTU-CVE-2020-16155

## What is CVE-2020-16155?

CVE-2020-16155 is a medium-severity vulnerability in n/a, published on 13 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The CPAN::Checksums package 2.12 for Perl does not uniquely define signed data.

## Which versions are affected by CVE-2020-16155?

It affects 1 product.


Products: Cpan\ \.

## How do I fix CVE-2020-16155?

Upgrade to a fixed version.

## Is CVE-2020-16155 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-16155 and fix it if it is affected.

What it is: CVE-2020-16155 is a medium-severity vulnerability in n/a, published on 13 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-16155 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-2020-16155/ (Markdown: https://insights.sbomify.com/CVE-2020-16155/index.md)
```

## Sources

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

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