CyberSecBulletin
CVE-2024-39791NVD status: Analyzed

VAR1200-H: Out-of-bounds Write

CVE-2024-39791 is a critical-severity out-of-bounds write vulnerability in VAR1200-H from Vonets, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected VAR1200-H versions: 3.3.23.6.9 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.11% chance of exploitation within 30 days, higher than 67% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Check which version of VAR1200-H you run against the affected versions below, and install the vendor's latest release.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
VonetsVAR1200-H3.3.23.6.9 and earlierNot stated
VonetsVAR1200-L3.3.23.6.9 and earlierNot stated
VonetsVAR600-H3.3.23.6.9 and earlierNot stated
VonetsVAP11AC3.3.23.6.9 and earlierNot stated
VonetsVAP11G-500S3.3.23.6.9 and earlierNot stated
VonetsVBG12003.3.23.6.9 and earlierNot stated
VonetsVAP11S-5G3.3.23.6.9 and earlierNot stated
VonetsVAP11S3.3.23.6.9 and earlierNot stated
VonetsVAR11N-3003.3.23.6.9 and earlierNot stated
VonetsVAP11G-3003.3.23.6.9 and earlierNot stated
VonetsVAP11N-3003.3.23.6.9 and earlierNot stated
VonetsVAP11G3.3.23.6.9 and earlierNot stated
VonetsVAP11G-5003.3.23.6.9 and earlierNot stated
VonetsVGA-10003.3.23.6.9 and earlierNot stated
Vonetsvar1200-h_firmware3.3.23.6.9 and earlierNot stated
Vonetsvar1200-l_firmware3.3.23.6.9 and earlierNot stated
Vonetsvar600-h_firmware3.3.23.6.9 and earlierNot stated
Vonetsvap11ac_firmware3.3.23.6.9 and earlierNot stated
Vonetsvap11g-500s_firmware3.3.23.6.9 and earlierNot stated
Vonetsvbg1200_firmware3.3.23.6.9 and earlierNot stated
Vonetsvap11s-5g_firmware3.3.23.6.9 and earlierNot stated
Vonetsvap11s_firmware3.3.23.6.9 and earlierNot stated
Vonetsvar11n-300_firmware3.3.23.6.9 and earlierNot stated
Vonetsvap11n-300_firmware3.3.23.6.9 and earlierNot stated
Vonetsvap11g_firmware3.3.23.6.9 and earlierNot stated

Version data comes from the organisation that assigned the CVE; 3 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.010.0CriticalCNA (hq.dhs.gov)
CVSS 3.110.0CriticalCNA (hq.dhs.gov)
CVSS 3.19.8CriticalNVD

Official description

Stack-based buffer overflow vulnerabilities affecting Vonets industrial wifi bridge relays and wifi bridge repeaters, software versions 3.3.23.6.9 and prior, enable an unauthenticated remote attacker to execute arbitrary code.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
  2. CVE record published.
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in VAR1200-H

All VAR1200-H vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.