CVE-2021-36531
First published: Fri Aug 27 2021(Updated: )
ngiflib 0.4 has a heap overflow in GetByte() at ngiflib.c:70 in NGIFLIB_NO_FILE mode, GetByte() reads memory buffer without checking the boundary.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| MiniUPnP | =0.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2021-36531?
CVE-2021-36531 is classified as a moderate severity vulnerability due to the heap overflow risk it presents.
How do I fix CVE-2021-36531?
To fix CVE-2021-36531, update ngiflib to the latest version that resolves the heap overflow issue.
What causes CVE-2021-36531?
CVE-2021-36531 is caused by the GetByte() function reading memory without proper boundary checks in NGIFLIB_NO_FILE mode.
Which versions of ngiflib are affected by CVE-2021-36531?
CVE-2021-36531 affects ngiflib version 0.4.
What are the potential impacts of CVE-2021-36531?
Exploitation of CVE-2021-36531 could lead to application crashes or arbitrary code execution due to the heap overflow.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/remedy
- agent/references
- agent/author
- agent/severity
- agent/last-modified-date
- agent/weakness
- agent/first-publish-date
- agent/description
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/miniupnp project
- canonical/miniupnp
- version/miniupnp/0.4