LiveActive security incident?Get immediate response
CVE Record

CVE-2022-3575: Frauscher Sensortechnik Diagnostic System FDS102 for FAdC R2 and FAdCi R2 configuration upload vulnerability

Frauscher Sensortechnik GmbH FDS102 for FAdC R2 and FAdCi R2 v2.8.0 to v2.9.1 are vulnerable to malicious code upload without authentication by using the configuration upload function. This could lead to a complete compromise of the FDS102 device.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This flaw lets an unauthenticated network attacker upload malicious code through the FDS102 configuration upload function. For rail diagnostic environments using affected Frauscher FDS102 versions, the business risk is device takeover with loss of confidentiality, integrity, and availability.

Executive priority

Treat this as urgent for any rail diagnostic environment with affected FDS102 systems. The issue is unauthenticated and can fully compromise the device, but urgency depends on whether those devices are deployed and reachable.

Technical view

CVE-2022-3575 is a CWE-434 unrestricted upload issue in Frauscher Diagnostic System FDS102 for FAdC R2 and FAdCi R2. The CVSS 3.1 score is 9.8, with network attack vector, no privileges, no user interaction, and high CIA impact.

Likely exposure

Exposure is limited to organizations running Frauscher FDS102 for FAdC R2 or FAdCi R2, especially versions described as v2.8.0 to v2.9.1. The bundle’s affected metadata only lists v2.8.0, so confirm exact scope with Frauscher PSIRT.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The risk remains high because exploitation is described as unauthenticated, network-accessible, low complexity, and capable of complete device compromise.

Researcher notes

The source bundle establishes product, impact, CWE-434 classification, and CVSS vector. It does not include exploit details, indicators of compromise, or a named fixed version. Version scope has a discrepancy between narrative description and affected metadata.

Mitigation direction

  • Check Frauscher PSIRT guidance for supported fixed versions or compensating controls.
  • Inventory FDS102 deployments and identify FAdC R2 or FAdCi R2 use.
  • Restrict configuration upload interfaces to trusted management networks only.
  • Remove internet or untrusted network reachability for affected FDS102 systems.
  • Prioritize upgrade or vendor-approved remediation for affected versions.

Validation and detection

  • Confirm FDS102 firmware/software version on each deployed device.
  • Verify whether configuration upload is reachable from untrusted networks.
  • Review device logs for unexpected configuration uploads or administrative changes.
  • Compare deployment versions against Frauscher PSIRT’s current advisory scope.
  • Document any affected operational environments and remediation owner.
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 · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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-3575 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
0Timeline events
0ADP providers
2Source links

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.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-3575Attack 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Frauscher SensortechnikDiagnostic System FDS102v2.8.0Listed
Weakness

CWE details

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

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.