Skip to content
Fencer Intel
medium —

GHSA-927q-g9w9-pm54 json

Panic in mp3-metadata due to the lack of bounds checking

published last yr. modified last yr. also RUSTSEC-2025-0027

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

The `get_id3()` methods used by `mp3_metadata::read_from_slice()` does not perform adequate bounds checking when recreating the tag due to the use of desynchronization.

Fixed in [Fix index error](https://github.com/GuillaumeGomez/mp3-metadata/pull/37), released as part of 0.4.0.

Patch / fix

  • crates.io mp3-metadata 0.4.0

Is GHSA-927q-g9w9-pm54 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io mp3-metadata
<0.4.0
>=0.0.0-0, <0.4.0
0.4.0

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel 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.