LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24019: A stack-based buffer overflow vulnerability exists in the urvpn_client http_connection_readcb functionality...

A stack-based buffer overflow vulnerability exists in the urvpn_client http_connection_readcb functionality of Milesight UR32L v32.3.0.5. A specially crafted network packet can lead to a buffer overflow. An attacker can send a malicious packet to trigger this vulnerability.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-24019 is a high-severity memory corruption flaw in Milesight UR32L v32.3.0.5. A malicious network packet can overflow memory in the device’s VPN client handling, potentially compromising confidentiality, integrity, and availability. Sources do not identify a fixed version or confirmed exploitation.

Executive priority

Treat as high priority for environments using Milesight UR32L routers, especially if reachable from broader networks. Business risk is device compromise or service disruption, but urgency depends on whether v32.3.0.5 is present and exposed.

Technical view

The issue is a CWE-120 stack-based buffer overflow in the urvpn_client http_connection_readcb functionality of Milesight UR32L v32.3.0.5. CVSS 3.1 is 8.1: network exploitable, high attack complexity, no privileges, no user interaction, unchanged scope, and high CIA impact.

Likely exposure

Exposure appears limited to Milesight UR32L devices running v32.3.0.5 where the affected urvpn_client network handling is reachable. The supplied sources do not list other Milesight models or versions as affected.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source confirms active exploitation. The described trigger is a specially crafted network packet. Attack complexity is high, but no credentials or user interaction are required.

Researcher notes

Do not broaden affected scope beyond Milesight UR32L v32.3.0.5 based on these sources. The record provides vulnerability class, affected functionality, trigger type, and CVSS vector, but not exploit maturity, patched version, or vendor mitigation details.

Mitigation direction

  • Identify any Milesight UR32L devices and confirm firmware version.
  • Check Milesight vendor guidance for fixed firmware or official mitigation.
  • Restrict device network exposure to trusted administrative or VPN networks.
  • Monitor affected devices for crashes, restarts, or unusual network traffic.
  • Prioritize replacement or compensating controls if no fix is available.

Validation and detection

  • Inventory UR32L assets and record firmware versions.
  • Verify whether any device runs v32.3.0.5.
  • Confirm whether the affected service is reachable from untrusted networks.
  • Review vendor advisories before declaring remediation complete.
  • Document compensating controls where patch status is unknown.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-24019 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2023-24019Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MilesightUR32Lv32.3.0.5Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.