# CVE-2022-23334: Security feature bypass in n/a

> Attackers can escalate privileges by replacing the remote manager executable due to weak signature checks in the Robot application.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-4847-3cw5-45xm

## What is CVE-2022-23334?

CVE-2022-23334 is a critical vulnerability in n/a, published on 30 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Robot application in Ip-label Newtest before v8.5R0 was discovered to use weak signature checks on executed binaries, allowing attackers to have write access and escalate privileges via replacing NEWTESTREMOTEMANAGER.EXE.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2022-23334?

It affects 1 product.


Products: Ip-Label Newtest.

## How do I fix CVE-2022-23334?

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

## Is CVE-2022-23334 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23334 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23334 and fix it if it is affected.

What it is: CVE-2022-23334 is a critical vulnerability in n/a, published on 30 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23334 exists.

Affected product: n/a. 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-2022-23334/ (Markdown: https://insights.sbomify.com/CVE-2022-23334/index.md)
```

## Sources

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

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