CVE-2024-3913: Phoenix Contact: Start sequence allows attack during the boot process
Published Aug 13, 2024
·Updated
An unauthenticated remote attacker can use this vulnerability to change the device configuration due to a file writeable for short time after system startup.
Affected Software
8 affected components
All of the following
Phoenixcontact Charx Sec-3150 Firmware<1.6.3
Phoenixcontact Charx Sec-3150
All of the following
Phoenixcontact Charx Sec-3100 Firmware<1.6.3
Phoenixcontact Charx Sec-3100
All of the following
Phoenixcontact Charx Sec-3050 Firmware<1.6.3
Phoenixcontact Charx Sec-3050
All of the following
Phoenixcontact Charx Sec-3000 Firmware<1.6.3
Phoenixcontact Charx Sec-3000
Event History
Aug 13, 2024
CVE Published
via MITRE·12:30 PM
Data Sourced
via MITRE·12:30 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 PM
DescriptionSeverityWeaknessAffected Software
Jul 19, 57049
Event
via MITRE·05:36 AM
Frequently Asked Questions
1
What is the severity of CVE-2024-3913?
CVE-2024-3913 is considered a critical severity vulnerability due to its potential for unauthorized device configuration changes.
2
How do I fix CVE-2024-3913?
To mitigate CVE-2024-3913, update the affected Phoenix Contact CHARX SEC firmware to version 1.6.3 or higher.
3
What devices are affected by CVE-2024-3913?
CVE-2024-3913 affects Phoenix Contact CHARX SEC-3000, 3050, 3100, and 3150 devices with firmware versions below 1.6.3.
4
Can CVE-2024-3913 be exploited remotely?
Yes, CVE-2024-3913 can be exploited by unauthenticated remote attackers due to a temporary writable file after system startup.
5
Is user authentication required to exploit CVE-2024-3913?
No, user authentication is not required to exploit CVE-2024-3913.