Skip to content
Fencer Vulns
medium 6.6

CVE-2022-1534 json

Buffer Over-read at parse_rawml.c:1416 in bfabiszewski/libmobi

published 2022-04-29 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-24831

cvss
6.6
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

Buffer Over-read at parse_rawml.c:1416 in GitHub repository bfabiszewski/libmobi prior to 0.11. The bug causes the program reads data past the end of the intented buffer. Typically, this can allow attackers to read sensitive information from other memory locations or cause a crash.

Patch / fix

  • bfabiszewski bfabiszewski/libmobi 0.11
  • libmobi Debian 14, Debian 13, Debian 12 0.11+dfsg-1

debian advisories DEBIAN-CVE-2022-1534

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-1534 updated cvss 7.7

libmobi: Buffer Over-read at parse_rawml.c:1416

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/9a90ffa1-38f5-4685-9c00-68ba9068ce3d referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 6.6 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
NVD 2.0 3.6 AV:L/AC:L/Au:N/C:P/I:N/A:P

Affected products

  • bfabiszewski bfabiszewski/libmobi

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.