Skip to content
Fencer Intel
medium 5.5

CVE-2022-36148 json

fdkaac commit 53fe239 was discovered to contain a floating point exception (FPE) via wav_open at /src/wav_reader.c.

published 4y ago modified 4mo ago also EUVD-2022-38869

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits
0
none known

Summary

fdkaac commit 53fe239 was discovered to contain a floating point exception (FPE) via wav_open at /src/wav_reader.c.

Patch / fix

  • fdkaac_project fdkaac 1.0.3
  • fdkaac Debian 14, Debian 13 1.0.6-0.1

debian advisories DEBIAN-CVE-2022-36148

  • fdkaac Ubuntu Pro 16.04 LTS 0.6.2-1ubuntu0.1~esm1
  • fdkaac Ubuntu Pro 18.04 LTS 0.6.3-1ubuntu0.18.04.1~esm1
  • fdkaac Ubuntu Pro 20.04 LTS 0.6.3-1ubuntu0.20.04.1~esm1
  • fdkaac Ubuntu Pro 22.04 LTS 1.0.0-1ubuntu0.22.04.1~esm1
  • fdkaac Ubuntu Pro 24.04 LTS 1.0.0-1ubuntu0.24.04.1~esm1

ubuntu advisories UBUNTU-CVE-2022-36148

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • fdkaac Alpine 3.24, Alpine 3.23, Alpine 3.22 +6 more 1.0.3-r0

alpine advisories ALPINE-CVE-2022-36148

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-36148 in your stack? 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

Exploit prediction

0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/nu774/fdkaac/issues/52 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Classification

Weakness

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.