CISA ADP Vulnrichment

Answer in brief

CVE-2022-42917 records a Unknown severity vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps FRRouting/FRRouting (generic), n/a/n/a (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 13, 2026Updated Sep 14, 2026Source checked Sep 14, 2026First seen by HOL Sep 13, 2026Material review Sep 14, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps FRRouting/FRRouting (generic), n/a/n/a (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
FRRouting/FRRoutinggeneric	>=0 <4.5	4.5
n/a/n/ageneric	n/a	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for FRRouting/FRRouting, n/a/n/a.
Review the reported fix. Update FRRouting/FRRouting to 4.5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 13, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 13, 2026

Sources and claim methodology

Upstream source description

In FRRouting FRR before 8.5, the service user (usually frr) can escalate its privileges to root by monitoring the configuration directory (/etc/frr) and replacing config files upon creation with, for example, symlinks to change the ownership of arbitrary files. This is a TOCTOU Race Condition caused by a combination of touch and chown.

Quoted source text, attributed separately from HOL analysis.