N6854A Geolocation server and N6841A RF Sensor…: Deserialization of Untrusted Data
CVE-2022-1660 is a critical-severity deserialization of untrusted data vulnerability in N6854A Geolocation server and N6841A RF Sensor software from Keysight, 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. The record lists version 2.3.0 as the first without the flaw, so updating N6854A Geolocation server and N6841A RF Sensor software to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 16.8% chance of exploitation within 30 days, which is in the top 2.91% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update N6854A Geolocation server and N6841A RF Sensor software to 2.3.0 or a later version.
- Update N6854a Firmware to 2.4.0 or a later version.
- Update N6841a Rf Firmware to 2.4.0 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Keysight | N6854A Geolocation server and N6841A RF Sensor software | all up to, but not including, 2.3.0 | 2.3.0 |
| Keysight | N6854a Firmware | before 2.4.0 | 2.4.0 |
| Keysight | N6841a Rf Firmware | before 2.4.0 | 2.4.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
- 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 system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | CNA (hq.dhs.gov) |
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 2.0 | 10.0 | High | NVD |
Official description
The affected products are vulnerable of untrusted data due to deserialization without prior authorization/authentication, which may allow an attacker to remotely execute arbitrary code.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
How developers prevent this class of flaw
- If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
- Explicitly define a final object() to prevent deserialization.
More Deserialization of Untrusted Data vulnerabilities (CWE-502)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/uscert/ics/advisories/icsa-22-146-01Third Party Advisory, US Government Resource
Recent Deserialization of Untrusted Data vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
- 9.8 Critical severity
- 8.8 High severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.