CVE-2024-34087
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 · uneditedAn SEH-based buffer overflow in the BPQ32 HTTP Server in BPQ32 6.0.24.1 allows remote attackers with access to the Web Terminal to achieve remote code execution via an HTTP POST /TermInput request.
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 · high confidenceA Structured Exception Handler (SEH) based buffer overflow vulnerability exists in the BPQ32 HTTP Server version 6.0.24.1. Attackers who have access to the Web Terminal interface can trigger the vulnerability by sending a specially crafted HTTP POST request to /TermInput, potentially executing arbitrary code on the target system.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 BPQ32 HTTP Server installation and versionLocate the BPQ32 installation directory and check the version information, typically found in the executable properties or in a version file within the program folder. Common paths include C:\Program Files\BPQ32 or similar. Run 'dir' or use file properties to view version details.Affected if The installed version is 6.0.24.1 or falls within the affected version range
-
Verify Web Terminal feature statusAccess the BPQ32 configuration interface or check configuration files for the Web Terminal feature. This is typically configured in the BPQ32.ini or through the web-based admin panel. Look for settings related to 'Web Terminal' or '/TermInput' endpoint enablement.Affected if Web Terminal feature is enabled and accessible to the attacker
-
Confirm HTTP server is running and accessibleCheck if the BPQ32 HTTP server process is running (via Task Manager or command line tools like 'netstat -an | findstr 80' or 'tasklist'). Verify network accessibility by attempting to reach the HTTP server port from a browser or curl command.Affected if HTTP server is running and exposed on a network interface accessible to potential attackers
-
Inspect for presence of vulnerable /TermInput endpointSend a test HTTP request to the /TermInput endpoint using a tool like curl (e.g., curl -X POST http://target:port/TermInput) to confirm the endpoint exists and is processing requests.Affected if The /TermInput endpoint responds and processes POST requests, indicating the vulnerable code path is present
You are affected if BPQ32 HTTP Server version 6.0.24.1 is installed and the Web Terminal feature is enabled, allowing access to the vulnerable /TermInput endpoint.
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 dataRestrict network access to the BPQ32 Web Terminal service to trusted users only, and apply any vendor patches or updates when available. If no patch exists, consider disabling the HTTP server or implementing additional input validation/length checking on the /TermInput endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34087 — 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-34087 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