CyberSecBulletin
CVE-2024-7695NVD status: Deferred

PT-7728 Series: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-7695 is a high-severity out-of-bounds write vulnerability in PT-7728 Series from Moxa, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected PT-7728 Series versions: 1.0 through 3.9. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.72% chance of exploitation within 30 days, higher than 54% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of PT-7728 Series you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on moxa.com for workarounds and exact fixed builds.
  3. 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
MoxaPT-7728 Series1.0 through 3.9Not stated
MoxaPT-7828 Series1.0 through 4.0Not stated
MoxaPT-G503 Series1.0 through 5.3Not stated
MoxaPT-G510 Series1.0 through 6.5Not stated
MoxaPT-G7728 Series1.0 through 6.4Not stated
MoxaPT-G7828 Series1.0 through 6.4Not stated
MoxaEDS-608 Series1.0 through 3.12Not stated
MoxaEDS-611 Series1.0 through 3.12Not stated
MoxaEDS-616 Series1.0 through 3.12Not stated
MoxaEDS-619 Series1.0 through 3.12Not stated
MoxaEDS-405A Series1.0 through 3.14Not stated
MoxaEDS-408A Series1.0 through 3.12Not stated
MoxaEDS-505A Series1.0 through 3.11Not stated
MoxaEDS-508A Series1.0 through 3.11Not stated
MoxaEDS-510A Series1.0 through 3.12Not stated
MoxaEDS-516A Series1.0 through 3.11Not stated
MoxaEDS-518A Series1.0 through 3.11Not stated
MoxaEDS-G509 Series1.0 through 3.10Not stated
MoxaEDS-P510 Series1.0 through 3.11Not stated
MoxaEDS-P510A Series1.0 through 3.11Not stated
MoxaEDS-510E Series1.0 through 5.5Not stated
MoxaEDS-518E Series1.0 through 6.3Not stated
MoxaEDS-528E Series1.0 through 6.3Not stated
MoxaEDS-G508E Series1.0 through 6.4Not stated
MoxaEDS-G512E Series1.0 through 6.4Not stated

Version data comes from the organisation that assigned the CVE; 26 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
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (moxa.com).

Scoring systemScoreSeverityScored by
CVSS 4.08.7HighCNA (moxa.com)
CVSS 3.17.5HighCNA (moxa.com)

Official description

Multiple switches are affected by an out-of-bounds write vulnerability. This vulnerability is caused by insufficient input validation, which allows data to be written to memory outside the bounds of the buffer. Successful exploitation of this vulnerability could result in a denial-of-service attack.

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. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in PT-7728 Series

All PT-7728 Series vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.