| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in libjxl up to 0.5. It has been rated as critical. The affected element is the function jxl::ModularFrameDecoder::DecodeGroup. Performing a manipulation results in out-of-bounds write.
This vulnerability is known as CVE-2021-45928. No exploit is available.
Upgrading the affected component is advised.
Details
A vulnerability, which was classified as critical, was found in libjxl up to 0.5. This affects the function jxl::ModularFrameDecoder::DecodeGroup. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 01/01/2022 as 360. The advisory is shared at bugs.chromium.org. This vulnerability is uniquely identified as CVE-2021-45928 since 12/31/2021. Technical details are known, but no exploit is available.
Upgrading to version 0.6 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
Website
- Product: https://github.com/libjxl/libjxl/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: libjxl 0.6
Patch: github.com
Timeline
12/31/2021 🔍01/01/2022 🔍
01/01/2022 🔍
01/05/2022 🔍
Sources
Product: github.comAdvisory: 360
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2021-45928 (🔍)
GCVE (CVE): GCVE-0-2021-45928
GCVE (VulDB): GCVE-100-189525
Entry
Created: 01/01/2022 10:30Updated: 01/05/2022 13:24
Changes: 01/01/2022 10:30 (42), 01/05/2022 13:24 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.