CVE-2021-39533: Buffer Overflow
First published: Mon Sep 20 2021(Updated: )
An issue was discovered in libslax through v0.22.1. slaxLexer() in slaxlexer.c has a heap-based buffer overflow.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Juniper Libslax | <=0.22.1 |
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-39533?
CVE-2021-39533 is classified with a high severity due to the potential for a heap-based buffer overflow leading to arbitrary code execution.
How do I fix CVE-2021-39533?
To fix CVE-2021-39533, update libslax to version 0.22.2 or later.
Which versions of libslax are affected by CVE-2021-39533?
CVE-2021-39533 affects libslax versions up to and including 0.22.1.
What type of vulnerability is CVE-2021-39533?
CVE-2021-39533 is a heap-based buffer overflow vulnerability.
What components are impacted by CVE-2021-39533?
CVE-2021-39533 specifically impacts the slaxLexer() function in slaxlexer.c within the libslax library.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/weakness
- agent/tags
- agent/author
- agent/description
- agent/first-publish-date
- agent/references
- agent/event
- agent/source
- vendor/juniper
- canonical/juniper libslax
- version/juniper libslax/0.22.1