# CVE-2021-3548: Information disclosure in dmg2img

> An attacker can leak memory layout information via improper buffer validation in dmg2img, potentially aiding further exploitation.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-3548, GHSA-x35m-q6gq-75g7, UBUNTU-CVE-2021-3548

## What is CVE-2021-3548?

CVE-2021-3548 is a high-severity vulnerability in dmg2img, published on 26 May 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in dmg2img through 20170502. dmg2img did not validate the size of the read buffer during memcpy() inside the main() function. This possibly leads to memory layout information leaking in the data. This might be used in a chain of vulnerability in order to reach code execution.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2021-3548?

It affects 1 product.


Products: Dmg2img Project Dmg2img.

## How do I fix CVE-2021-3548?

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

## Is CVE-2021-3548 being exploited?

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

## Other vulnerabilities in dmg2img

- [CVE-2021-32614](https://insights.sbomify.com/CVE-2021-32614/): Information disclosure in dmg2img (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3548 and fix it if it is affected.

What it is: CVE-2021-3548 is a high-severity vulnerability in dmg2img, published on 26 May 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-3548 in the wild and no public exploit code.

Affected product: dmg2img. 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-2021-3548/ (Markdown: https://insights.sbomify.com/CVE-2021-3548/index.md)
```

## Sources

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

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