CVE-2022-1660 in the critical feed json
Keysight N6854A Geolocation server and N6841A RF Sensor software
published 2022-05-31 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-24946
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 16.8%
- EPSS 16.8% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Keysight N6854A Geolocation server and N6841A RF Sensor software 2.3.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-22-146-01 updated cvss 9.8
Keysight N6854A Geolocation server and N6841A RF Sensor software
-
Keysight Technologies, Inc. Keysight N6854A and N6841A RF <= 2.3.0affected: mitigation “Keysight recommends users update N6854A and N6841A RF to v2.4.0 or later.” keysight.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
16.82% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- Keysight N6854A Geolocation server and N6841A RF Sensor software
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
cisa.gov
/uscert/ics/advisories/icsa-22-146-01
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2022-1660
- NVD CVE-2022-1660
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.