# CVE-2022-1908: Buffer Over-read in bfabiszewski/libmobi

> A buffer over-read in the libmobi library allows attackers to cause denial of service or disclose sensitive information via crafted MOBI files.

- **Severity:** Low 3.6 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L`)
- **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:** Yes
- **Published:** 27 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-1908, GHSA-fg95-xw2v-r64x, UBUNTU-CVE-2022-1908

## What is CVE-2022-1908?

CVE-2022-1908 is a low-severity memory corruption vulnerability in bfabiszewski/libmobi, published on 27 May 2022. 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

Buffer Over-read in GitHub repository bfabiszewski/libmobi prior to 0.11.

Weakness: CWE-125 (Out-of-bounds Read), CWE-126 (Buffer Over-read)

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

It affects 1 product.


Products: Libmobi Project Libmobi.

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

Upgrade to a fixed version.

## Is CVE-2022-1908 being exploited?

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

## Other vulnerabilities in bfabiszewski/libmobi

- [CVE-2021-3751](https://insights.sbomify.com/CVE-2021-3751/): Out-of-bounds Write in bfabiszewski/libmobi (critical 9.6)
- [CVE-2018-11724](https://insights.sbomify.com/CVE-2018-11724/): Memory corruption in n/a (high 8.8)
- [CVE-2018-11726](https://insights.sbomify.com/CVE-2018-11726/): Memory corruption in n/a (high 8.8)
- [CVE-2018-11438](https://insights.sbomify.com/CVE-2018-11438/): Memory corruption in n/a (high 8.8)
- [CVE-2021-3888](https://insights.sbomify.com/CVE-2021-3888/): Use of Out-of-range Pointer Offset in bfabiszewski/libmobi (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1908 is a low-severity memory corruption vulnerability in bfabiszewski/libmobi, published on 27 May 2022. 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-2022-1908 in the wild and no public exploit code.

Affected product: bfabiszewski/libmobi. 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-1908/ (Markdown: https://insights.sbomify.com/CVE-2022-1908/index.md)
```

## Sources

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

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