CyberSecBulletin
CVE-2022-37454NVD status: Modified

RUGGEDCOM APE1808: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2022-37454 is a critical-severity integer overflow or wraparound vulnerability in RUGGEDCOM APE1808 from Siemens, 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 RUGGEDCOM APE1808 versions: all versions. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 7.41% chance of exploitation within 30 days, which is in the top 5.46% of all scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update SIMATIC S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5 or a later version.
  2. Update SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP to V3.1.5 or a later version.
  3. Update SIPLUS S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5 or a later version.
  4. Read the advisory on github.com for workarounds and exact fixed builds.
  5. 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
SiemensRUGGEDCOM APE1808all versionsNot stated
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFPV3.1.0 up to, but not including, V3.1.5V3.1.5
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFPV3.1.0 up to, but not including, V3.1.5V3.1.5
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFPV3.1.0 up to, but not including, V3.1.5V3.1.5
Extended Keccak Code Package ProjectExtended Keccak Code PackageNot specified in the recordNot stated
DebianDebian Linux10.0; 11.0Not stated
Fedora ProjectFedora35; 36Not stated
PHPPHP7.2.0 up to, but not including, 7.4.33; 8.0.0 up to, but not including, 8.0.25; 8.1.0 up to, but not including, 8.1.127.4.33, 8.0.25, 8.1.12
PythonPython3.6.0 up to, but not including, 3.7.16; 3.8.0 up to, but not including, 3.8.16; 3.9.0 up to, but not including, 3.9.16; 3.10.0 up to, but not including, 3.10.93.7.16, 3.8.16, 3.9.16, 3.10.9
Sha3 ProjectSha3before 1.0.51.0.5
Pysha3 ProjectPysha3Not specified in the recordNot stated
PypyPypy7.0.0 and laterNot stated

Version data comes from the organisation that assigned the CVE. 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 3.19.8CriticalNVD
CVSS 3.19.8CriticalCISA (ADP)

Official description

The Keccak XKCP SHA-3 reference implementation before fdc6fef has an integer overflow and resultant buffer overflow that allows attackers to execute arbitrary code or eliminate expected cryptographic properties. This occurs in the sponge function interface.

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

The underlying weakness: Integer Overflow or Wraparound

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How developers prevent this class of flaw

  • Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).

More Integer Overflow or Wraparound vulnerabilities (CWE-190)

Timeline

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

References

Technical write-ups (may include proof of concept)

Other vulnerabilities in RUGGEDCOM APE1808

All RUGGEDCOM APE1808 vulnerabilities

Recent Integer Overflow or Wraparound vulnerabilities

Spotted an error? Tell us.