SICK InspectorP61x: Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking
CVE-2024-10772 is a high-severity reliance on obfuscation or encryption of security-relevant inputs without integrity checking vulnerability in SICK InspectorP61x from SICK, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version <5.0.0 as the first without the flaw, so updating SICK InspectorP61x to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.34% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update SICK InspectorP61x to <5.0.0 or a later version.
- Update SICK InspectorP62x to <5.0.0 or a later version.
- Update inspector61x_firmware to 5.0.0 or a later version.
- Read the advisory on sick.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| SICK | SICK InspectorP61x | before <5.0.0 | <5.0.0 |
| SICK | SICK InspectorP62x | before <5.0.0 | <5.0.0 |
| Sick | inspector61x_firmware | before 5.0.0 | 5.0.0 |
| Sick | inspector62x_firmware | before 5.0.0 | 5.0.0 |
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
- LowA basic user account is enough.
- 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:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (sick.de).
Official description
Since the firmware update is not validated, an attacker can install modified firmware on the device. This has a high impact on the availabilty, integrity and confidentiality up to the complete compromise of the device.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking
The product uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the product does not use integrity checks to detect if those inputs have been modified.
How developers prevent this class of flaw
- Protect important client controllable tokens/parameters for integrity using PKI methods (i.e. digital signatures) or other means, and checks for integrity on the server side.
- Repeated requests from a particular user that include invalid values of tokens/parameters (those that should not be changed manually by users) should result in the user account lockout.
- Client side tokens/parameters should not be such that it would be easy/predictable to guess another valid state.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
Other vulnerabilities in SICK InspectorP61x
- 8.2 High severity
- 7.3 High severity
- 9.0 Critical severity
- 8.8 High severity
Spotted an error? Tell us.