LiveActive security incident?Get immediate response
CVE Record

CVE-2022-23334: The Robot application in Ip-label Newtest before v8.5R0 was discovered to use weak signature checks on exec...

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Ip-label Newtest before v8.5R0 has a critical trust-checking flaw in its Robot application. Public records say weak signature validation of executed binaries could let an attacker replace a Newtest executable and gain higher privileges, potentially affecting confidentiality, integrity, and availability.

Executive priority

Treat this as urgent for environments running affected Newtest Robot software. The high CVSS score and privilege escalation impact justify rapid inventory, vendor-guided remediation, and access-control review.

Technical view

CVE-2022-23334 is mapped to CWE-347 and scored CVSS 3.1 9.8 with AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The described issue is weak signature verification for executed binaries, specifically replacement of NEWTESTREMOTEMANAGER.EXE in the Robot application before v8.5R0.

Likely exposure

Exposure is most likely where Ip-label Newtest Robot components older than v8.5R0 are installed, especially on systems where attackers can influence executable files. The provided affected CPE data is incomplete.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The public description indicates privilege escalation through binary replacement, but does not provide complete environmental prerequisites.

Researcher notes

Public data is sparse: affected vendor/product fields are listed as n/a in the bundle, while the description names Ip-label Newtest Robot before v8.5R0. Do not assume broader Ekara/Newtest component exposure without vendor evidence.

Mitigation direction

  • Identify all Ip-label Newtest Robot deployments and versions.
  • Prioritize upgrade to v8.5R0 or later if vendor guidance confirms remediation.
  • Restrict write access to Newtest installation and executable directories.
  • Review vendor or ON-X advisory for supported remediation details.
  • Increase monitoring for unexpected Newtest binary changes.

Validation and detection

  • Confirm whether Robot application versions are earlier than v8.5R0.
  • Inventory hosts containing NEWTESTREMOTEMANAGER.EXE.
  • Check file integrity and signing status for Newtest executables.
  • Review endpoint logs for unexpected executable replacement or privilege changes.
  • Document whether compensating controls restrict installation directory writes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-347: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-23334 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-23334Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-347 · source CWE mapping

Improper Verification of Cryptographic Signature

Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.