Forensia: Free Threat Intelligence Lookup

FORENSIA

Indicator investigation

warming up…

Resolving indicator evidenceacquiring

Loading verdict, provenance, relationships and sightings.

Opening Forensia workspaceacquiring

Loading the current evidence view. Navigation and account controls remain available.

Loading recent evidenceacquiring

Verdict

CRITICAL SEVERITY (CVSS 9.1)

What is this: MOOS-IvP uFldNodeBroker through 24.8.1 fails to validate the source of TRY_SHORE_HOST messages on the vehicle bus, allowing any publisher to enroll at… (CWE-345)
Should you care: Rated critical severity — CVSS 9.1.
What to do: Patch when able.

INVESTIGATEMODERATE EVIDENCE COVERAGEDeterministic · stored evidence only

Vulnerability investigation

Critical technical impact; exploitation evidence is not established

CISA KEV status could not be verified from the available evidence. NVD rates the technical severity critical at CVSS 9.1. These are public vulnerability signals, not proof that a specific environment runs an affected version.

Exploitation status

KEV status unavailable

The KEV source did not return a conclusive status.

30-day exploitation likelihood

Unavailable

FIRST EPSS did not return a score.

Technical severity

9.1 · critical

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

Affected surface

Product applicability incomplete

No structured product mapping is available.

Weakness class

CWE-345

CWE describes the weakness category, not whether a deployed product is reachable or exploitable.

Corpus evidence

1 connectors · 2 citations

No related report text is available in the local corpus.

What the evidence supports

Findings stay bounded to named sources and observable infrastructure.

1 finding

CVSS 9.1 critical technical impact

HIGH

Network · Low · None

NIST NVD CVSS

CVSS measures technical severity and prerequisites; it does not measure observed exploitation likelihood.

What remains unknown

Whether your environment runs an affected product and version is not established by this public lookup.
Reachability, compensating controls, and successful exploitation in a specific environment are not checked.
No reliable product/version mapping is available, so applicability remains unresolved.
CISA KEV status is unavailable and must be retried before drawing an exploitation conclusion.
No locally ingested public report supplies exploit, actor, or campaign context for this CVE.

What this is

MOOS-IvP uFldNodeBroker through 24.8.1 fails to validate the source of TRY_SHORE_HOST messages on the vehicle bus, allowing any publisher to enroll attacker-controlled shore routes. Attackers can publish malicious shore route messages to receive bridged vehicle traffic including sensor data and control information.

Evidence readiness

The base CVE appears first. Independent evidence is added without blocking the page.

Investigation status

Checking for newly completed evidence

Refreshing

NIST NVD

NVD evidence is available in this response

Ready

CISA KEV

Known-exploitation catalog check is pending

Pending

FIRST EPSS

Forensia does not request or publish EPSS while source rights are under review

Rights pending

Reports

Report links are still being resolved

Pending

Relationships

Product and vulnerability relationships are still being prepared

Pending

related indicators · 14 connectors · 1

Graph preview

Neighborhood topology. Open the graph for interactive pivots.

Open full investigation canvas →

Building relationship previewacquiring

Loading connected indicators, reports and entities.

Continue investigation

High-signal pivots without leaving the thread you started in search.

Related alerts, reports, and entities
Structured pivots from local graph context.
Open in graph
Full investigation canvas with neighbor expansion.