Integer Overflow or Wraparound The advisory has been revoked - it doesn't affect any version of package libreoffice:flatpak/gstreamer1-plugins-good-debugsource  (opens in a new tab)


Threat Intelligence

EPSS
0.43% (37th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-LIBREOFFICE-4458820
  • published30 Sept 2022
  • disclosed18 May 2022

Introduced: 18 May 2022

CVE-2022-1924  (opens in a new tab)
CWE-190  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:8.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libreoffice:flatpak/gstreamer1-plugins-good-debugsource package and not the libreoffice:flatpak/gstreamer1-plugins-good-debugsource package as distributed by RHEL.

DOS / potential heap overwrite in mkv demuxing using lzo decompression. Integer overflow in matroskademux element in lzo decompression function which causes a segfault, or could cause a heap overwrite, depending on libc and OS. Depending on the libc used, and the underlying OS capabilities, it could be just a segfault or a heap overwrite. If the libc uses mmap for large chunks, and the OS supports mmap, then it is just a segfault (because the realloc before the integer overflow will use mremap to reduce the size of the chunk, and it will start to write to unmapped memory). However, if using a libc implementation that does not use mmap, or if the OS does not support mmap while using libc, then this could result in a heap overwrite.