CVE-2025-41666
Phoenix Contact: File access due to the replacement of a critical file used by the watchdog
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2025.0.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A low privileged remote attacker with file access can replace a critical file used by the watchdog to get read, write and execute access to any file on the device after the watchdog has been initialized.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- PHOENIX CONTACT AXC F 1152
fixed in 2025.0.2
- PHOENIX CONTACT AXC F 2152
fixed in 2025.0.2
- PHOENIX CONTACT AXC F 3152
fixed in 2025.0.2
- PHOENIX CONTACT BPC 9102S
fixed in 2025.0.2
- PHOENIX CONTACT RFC 4072S
fixed in 2025.0.2