# CVE-2022-35009: Denial of service in n/a

> A memory allocation flaw in PNGDec allows attackers to cause a denial of service via crafted input.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2463-wg6r-r9mf

## What is CVE-2022-35009?

CVE-2022-35009 is a medium-severity denial of service vulnerability in n/a, published on 16 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

PNGDec commit 8abf6be was discovered to contain a memory allocation problem via asan_malloc_linux.cpp.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Pngdec Project Pngdec.

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

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

## Is CVE-2022-35009 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-35011](https://insights.sbomify.com/CVE-2022-35011/): Memory corruption in n/a (high 8.8)
- [CVE-2022-35007](https://insights.sbomify.com/CVE-2022-35007/): Memory corruption in n/a (medium 6.5)
- [CVE-2022-35008](https://insights.sbomify.com/CVE-2022-35008/): Memory corruption in n/a (medium 6.5)
- [CVE-2022-35010](https://insights.sbomify.com/CVE-2022-35010/): Memory corruption in n/a (medium 6.5)
- [CVE-2022-35012](https://insights.sbomify.com/CVE-2022-35012/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-35009 is a medium-severity denial of service vulnerability in n/a, published on 16 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-35009 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-2022-35009/ (Markdown: https://insights.sbomify.com/CVE-2022-35009/index.md)
```

## Sources

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

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