Skip to main content
VulnerabilityPublished Updated

CVE-2024-34087: BPQ32 · Stack-based Buffer Overflow

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Immediately restrict network access to the BPQ32 HTTP Server web terminal, especially the /TermInput endpoint, using firewalls or access control lists to limit exposure to trusted IP addresses only.
  2. Monitor network traffic for unusual or malformed HTTP POST requests targeting /TermInput and implement intrusion detection/prevention rules to block exploitation attempts.
  3. If possible, disable the web terminal interface temporarily until a vendor patch or official fix is released.
  4. Employ application-layer gateways or reverse proxies that can sanitize or block suspicious input before it reaches the BPQ32 server.
  5. Conduct thorough audits of BPQ32 deployments to identify exposed instances and ensure they are not accessible from untrusted networks.
  6. Prepare incident response plans specific to BPQ32 compromise scenarios, including forensic data collection and system recovery procedures.
  7. Engage with the BPQ32 vendor or community for updates on patches or mitigations and apply them promptly once available.
  8. Consider network segmentation to isolate BPQ32 servers from general user networks to reduce attack surface.

Description

An 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.

References

Community reviews

Loading reviews…