Webmproject
Products by Webmproject Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2024 there have been 0 vulnerabilities in Webmproject . Last year Webmproject had 4 security vulnerabilities published. Right now, Webmproject is on track to have less security vulnerabilities in 2024 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2024 | 0 | 0.00 |
| 2023 | 4 | 7.93 |
| 2022 | 0 | 0.00 |
| 2021 | 11 | 9.21 |
| 2020 | 0 | 0.00 |
| 2019 | 1 | 7.50 |
| 2018 | 3 | 8.37 |
It may take a day or so for new Webmproject vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Webmproject Security Vulnerabilities
VP9 in libvpx before 1.13.1 mishandles widths
CVE-2023-44488
7.5 - High
- September 30, 2023
VP9 in libvpx before 1.13.1 mishandles widths, leading to a crash related to encoding.
Improper Handling of Exceptional Conditions
** REJECT ** This CVE ID has been rejected or withdrawn by its CVE Numbering Authority
CVE-2023-5129
- September 25, 2023
** REJECT ** This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Duplicate of CVE-2023-4863.
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2
CVE-2023-4863
8.8 - High
- September 12, 2023
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical)
Memory Corruption
There exists a use after free/double free in libwebp
CVE-2023-1999
7.5 - High
- June 20, 2023
There exists a use after free/double free in libwebp. An attacker can use the ApplyFiltersAndEncode() function and loop through to free best.bw and assign best = trial pointer. The second loop will then return 0 because of an Out of memory error in VP8 encoder, the pointer is still assigned to trial and the AddressSanitizer will attempt a double free.
Double-free
A flaw was found in libwebp in versions before 1.0.1
CVE-2020-36328
9.8 - Critical
- May 21, 2021
A flaw was found in libwebp in versions before 1.0.1. A heap-based buffer overflow in function WebPDecodeRGBInto is possible due to an invalid check for buffer size. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Memory Corruption
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE16().
CVE-2018-25009
9.1 - Critical
- May 21, 2021
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE16().
Out-of-bounds Read
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ApplyFilter().
CVE-2018-25010
9.1 - Critical
- May 21, 2021
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ApplyFilter().
Out-of-bounds Read
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in PutLE16().
CVE-2018-25011
9.8 - Critical
- May 21, 2021
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in PutLE16().
Memory Corruption
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE24().
CVE-2018-25012
9.1 - Critical
- May 21, 2021
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE24().
Out-of-bounds Read
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ShiftBytes().
CVE-2018-25013
9.1 - Critical
- May 21, 2021
A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ShiftBytes().
Out-of-bounds Read
A use of uninitialized value was found in libwebp in versions before 1.0.1 in ReadSymbol().
CVE-2018-25014
9.8 - Critical
- May 21, 2021
A use of uninitialized value was found in libwebp in versions before 1.0.1 in ReadSymbol().
Use of Uninitialized Resource
A flaw was found in libwebp in versions before 1.0.1
CVE-2020-36329
9.8 - Critical
- May 21, 2021
A flaw was found in libwebp in versions before 1.0.1. A use-after-free was found due to a thread being killed too early. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Dangling pointer
A flaw was found in libwebp in versions before 1.0.1
CVE-2020-36330
9.1 - Critical
- May 21, 2021
A flaw was found in libwebp in versions before 1.0.1. An out-of-bounds read was found in function ChunkVerifyAndAssign. The highest threat from this vulnerability is to data confidentiality and to the service availability.
Out-of-bounds Read
A flaw was found in libwebp in versions before 1.0.1
CVE-2020-36331
9.1 - Critical
- May 21, 2021
A flaw was found in libwebp in versions before 1.0.1. An out-of-bounds read was found in function ChunkAssignData. The highest threat from this vulnerability is to data confidentiality and to the service availability.
Out-of-bounds Read
A flaw was found in libwebp in versions before 1.0.1
CVE-2020-36332
7.5 - High
- May 21, 2021
A flaw was found in libwebp in versions before 1.0.1. When reading a file libwebp allocates an excessive amount of memory. The highest threat from this vulnerability is to the service availability.
Resource Exhaustion
In libwebm before 2019-03-08, a NULL pointer dereference caused by the functions OutputCluster and OutputTracks in webm_info.cc will trigger an abort, which
CVE-2019-9746
7.5 - High
- March 13, 2019
In libwebm before 2019-03-08, a NULL pointer dereference caused by the functions OutputCluster and OutputTracks in webm_info.cc will trigger an abort, which allows a DoS attack, a similar issue to CVE-2018-19212.
NULL Pointer Dereference
In libwebm through 2018-10-03, there is an abort caused by libwebm::Webm2Pes::InitWebmParser()
CVE-2018-19212
6.5 - Medium
- November 12, 2018
In libwebm through 2018-10-03, there is an abort caused by libwebm::Webm2Pes::InitWebmParser() that will lead to a DoS attack.
Always-Incorrect Control Flow Implementation
A use-after-free issue was discovered in libwebm through 2018-02-02
CVE-2018-6548
9.8 - Critical
- February 02, 2018
A use-after-free issue was discovered in libwebm through 2018-02-02. If a Vp9HeaderParser was initialized once before, its property frame_ would not be changed because of code in vp9parser::Vp9HeaderParser::SetFrame. Its frame_ could be freed while the corresponding pointer would not be updated, leading to a dangling pointer. This is related to the function OutputCluster in webm_info.cc.
Dangling pointer
The function ParseVP9SuperFrameIndex in common/libwebm_util.cc in libwebm through 2018-01-30 does not validate the child_frame_length data obtained from a .webm file, which
CVE-2018-6406
8.8 - High
- January 30, 2018
The function ParseVP9SuperFrameIndex in common/libwebm_util.cc in libwebm through 2018-01-30 does not validate the child_frame_length data obtained from a .webm file, which allows remote attackers to cause an information leak or a denial of service (heap-based buffer over-read and later out-of-bounds write), or possibly have unspecified other impact.
Out-of-bounds Read
VP8 Codec SDK (libvpx) before 1.0.0 "Duclair"
CVE-2012-0823
- February 23, 2012
VP8 Codec SDK (libvpx) before 1.0.0 "Duclair" allows remote attackers to cause a denial of service (application crash) via (1) unspecified "corrupt input" or (2) by "starting decoding from a P-frame," which triggers an out-of-bounds read, related to "the clamping of motion vectors in SPLITMV blocks".
Improper Input Validation