Skip to main content
No exploitation reported

CVE-2022-29519

No exploitation reported by the sources we read.

  • Published2022-06-28
  • WeaknessCWE-319

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Cleartext transmission of sensitive information vulnerability exists in STARDOM FCN Controller and FCJ Controller R1.01 to R4.31, which may allow an adjacent attacker to login the affected products and alter device configuration settings or tamper with device firmware.

Timeline

dates in UTC
  1. 2022-06-2813:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-29519?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-29519?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Yokogawa stardom fcj firmwareversion to verify
BranchAffectedFixed in
—≥ r1.01, ≤ r4.31no fix published
Yokogawa stardom fcn firmwareversion to verify
BranchAffectedFixed in
—≥ r1.01, ≤ r4.31no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • ICSA-22-174-01 CISA1 known affected

    Yokogawa STARDOM

    STARDOM FCN/FCJ: Versions R1.01 through R4.31

Full record on NVD

Fix

  1. Mitigation from the vendor CISA ICSA-22-174-01 · 2 productsEnable the packet filtering functionality of the FCN/FCJ controller to only allow connections from trusted hosts.
  2. Mitigation from the vendor CISA ICSA-22-174-01 · 2 productsEnsure network traffic cannot be captured by unauthorized users.
  3. Mitigation from the vendor CISA ICSA-22-174-01 · 2 productsYokogawa strongly recommends users establish and maintain an operational security program, including regular patching, anti-virus, backup and recovery processes, network segmentation, hardened networks, whitelisting, firewalls, etc. Yokogawa can assist users in setting up and maintaining these secu…
  4. Mitigation from the vendor CISA ICSA-22-174-01 · 2 productsYokogawa considers patching to be the best mitigation against these vulnerabilities. Users are encouraged to contact Yokogawa to discuss the best course of action for individual systems.
  5. Mitigation from the vendor CISA ICSA-22-174-01 · 2 productsSee Yokogawa's security advisory report YSAR-22-007 for more information.

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.17.5read 2026-10-23
  • NVDCVSS 2.07.9read 2026-10-23
  • NVDweakness (CWE)CWE-319read 2026-10-23
  • FIRST EPSSEPSS score0.4 %2026-10-22

Technical details

CVSS v3 Vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2022-06-28
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2022-29519?

Cleartext transmission of sensitive information vulnerability exists in STARDOM FCN Controller and FCJ Controller R1.01 to R4.31, which may allow an adjacent attacker to login the affected products and alter device configuration settings or tamper with device firmware.

Is CVE-2022-29519 actively exploited?

Active exploitation of CVE-2022-29519 has not been confirmed. Its EPSS score was 0.4% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-29519?

CVE-2022-29519 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running Yokogawa STARDOM? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month