# CVE-2023-1399: Deserialization in N6854A Geolocation Server

> Untrusted data deserialization in Keysight N6854A Geolocation Server allows remote attackers to escalate privileges and execute code.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2023
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-c7p4-qvpp-vjjq

## What is CVE-2023-1399?

CVE-2023-1399 is a high-severity unsafe deserialization vulnerability in Keysight Technologies N6854A Geolocation Server, published on 27 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

N6854A Geolocation Server versions 2.4.2 are vulnerable to untrusted data deserialization, which may allow a malicious actor to escalate privileges in the affected device’s default configuration and achieve remote code execution.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2023-1399?

It affects 1 product.


Products: Keysight N6854a Firmware.

## How do I fix CVE-2023-1399?

No fix has been published for CVE-2023-1399 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-1399 being exploited?

There is no known exploitation of CVE-2023-1399 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-1399 and fix it if it is affected.

What it is: CVE-2023-1399 is a high-severity unsafe deserialization vulnerability in Keysight Technologies N6854A Geolocation Server, published on 27 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-1399 in the wild and no public exploit code.

Affected product: Keysight Technologies N6854A Geolocation Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-1399/ (Markdown: https://insights.sbomify.com/CVE-2023-1399/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-1399
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-1399
- OSV: https://osv.dev/vulnerability/CVE-2023-1399

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-1399/
Summaries are generated and may contain mistakes; the official description above is the record.