Skip to main content
CVE-2023-49262VulnerabilityPublished Updated

CVE-2023-49262: Hongdian H8951-4G-ESP · Integer Overflow or Wraparound

Affects Hongdian H8951-4G-ESPSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% 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 12 Jan 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Hongdian H8951-4G-ESPAffected
  • =0
Fixed in–

AI-suggested

1. Immediate network segmentation: Isolate Hongdian H8951-4G-ESP devices from general network access to limit exposure. 2. Restrict management interface access: Enforce strict access control lists (ACLs) and use VPNs or dedicated management networks to reduce attack surface. 3. Monitor active sessions: Implement session monitoring and anomaly detection to identify unusual cookie values or session behaviors indicative of exploitation attempts. 4. Apply virtual patching: Use intrusion prevention systems (IPS) or web application firewalls (WAF) to detect and block malformed authentication cookie payloads targeting this overflow. 5. Vendor engagement: Engage with Hongdian for official patches or firmware updates and prioritize their deployment once available. 6. Incident response readiness: Prepare for potential compromise by backing up configurations, logging access, and having remediation plans. 7. User session hygiene: Enforce session timeouts and multi-factor authentication where possible to reduce the risk of session hijacking that could enable exploitation.

Description

The authentication mechanism can be bypassed by overflowing the value of the Cookie "authentication" field, provided there is an active user session.

References

Community reviews

Loading reviews…