# CVE-2022-4976: Supply chain in Archive::Unzip::Burst

> The Perl Archive::Unzip::Burst library bundles a vulnerable InfoZip version, exposing users to known security flaws in the underlying dependency.

- **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:** No
- **Published:** 12 Jun 2025
- **Updated:** 13 Jun 2025
- **Also known as:** GHSA-x95w-6xxq-wrf2

## What is CVE-2022-4976?

CVE-2022-4976 is a critical vulnerability in ETJ Archive::Unzip::Burst, published on 12 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Archive::Unzip::Burst from 0.01 through 0.09 for Perl contains a bundled InfoZip library that is affected by several vulnerabilities.

The bundled library is affected by CVE-2014-8139, CVE-2014-8140 and CVE-2014-8141.

Weakness: CWE-1395 (Dependency on Vulnerable Third-Party Component)

## Which versions are affected by CVE-2022-4976?


## How do I fix CVE-2022-4976?

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

## Is CVE-2022-4976 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4976 and fix it if it is affected.

What it is: CVE-2022-4976 is a critical vulnerability in ETJ Archive::Unzip::Burst, published on 12 Jun 2025. 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-2022-4976 in the wild and no public exploit code.

Affected product: ETJ Archive::Unzip::Burst. 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-2022-4976/ (Markdown: https://insights.sbomify.com/CVE-2022-4976/index.md)
```

## Sources

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

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