CVE-2024-35333
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA stack-buffer-overflow vulnerability exists in the read_charset_decl function of html2xhtml 1.3. This vulnerability occurs due to improper bounds checking when copying data into a fixed-size stack buffer. An attacker can exploit this vulnerability by providing a specially crafted input to the vulnerable function, causing a buffer overflow and potentially leading to arbitrary code execution, denial of service, or data corruption.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStack-buffer-overflow vulnerability in html2xhtml 1.3's read_charset_decl function due to improper bounds checking when copying data into a fixed-size stack buffer. Exploitation via specially crafted input can lead to arbitrary code execution, DoS, or data corruption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if html2xhtml is installedRun 'which html2xhtml' or check common installation paths like /usr/bin/html2xhtml, /usr/local/bin/html2xhtml. On Windows, check Program Files directories.Affected if html2xhtml executable exists on the system
-
Determine the installed versionRun 'html2xhtml --version' or 'html2xhtml -v'. If no version flag works, check the binary's metadata or package information if installed via a package manager.Affected if The version reported is 1.3 or earlier (1.3 is explicitly listed as affected)
-
Locate the executable and confirm it contains the vulnerable functionUse 'strings' or a disassembler on the html2xhtml binary to search for 'read_charset_decl' - the function name mentioned in the CVE.Affected if The binary contains references to read_charset_decl function
-
Identify input processing conditionsTest html2xhtml with HTML input containing charset declarations (e.g., <meta http-equiv="Content-Type" content="text/html; charset=...">). The vulnerability triggers when parsing charset declarations.Affected if The tool processes HTML files with charset declarations using the vulnerable function
A user is affected if html2xhtml version 1.3 is installed and processes HTML input containing charset declarations that trigger the read_charset_decl function.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper bounds checking in the read_charset_decl function to validate input length before copying data into the fixed-size stack buffer. Input validation and safe string handling functions should be used.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35333 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-35333 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data