{"vulnerability": "cve-2024-4365", "sightings": [{"uuid": "af5c58ed-0305-496b-8d6f-9b73969bd0e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43652", "type": "seen", "source": "https://t.me/cvedetector/14817", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43652 - \"Iocharger AC Firmware Command Injection Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-43652 \nPublished : Jan. 9, 2025, 8:15 a.m. | 40\u00a0minutes ago \nDescription : Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root  \nThis issue affects Iocharger firmware for AC model chargers before version 24120701  \n  \nLikelihood: Moderate \u2013 The  binary does not seem to be used by the web interface, so it might be more difficult to find. It seems to be largely the same binary as used by the Iocharger Pedestal charging station, however. The attacker will also need a (low privilege) account to gain access to the  binary, or convince a user with such access to execute a crafted HTTP request.  \n  \nImpact: Critical \u2013 The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete  \nfiles and services. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-09T10:14:03.000000Z"}, {"uuid": "18d884e5-0e41-4211-a0d8-a5760d2243d1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43651", "type": "seen", "source": "https://t.me/cvedetector/14816", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43651 - Iocharger AC Model Command Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-43651 \nPublished : Jan. 9, 2025, 8:15 a.m. | 40\u00a0minutes ago \nDescription : Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root  \nThis issue affects Iocharger firmware for AC models before version 241207101  \n  \nLikelihood: Moderate \u2013 The  binary does not seem to be used by the web interface, so it might be more difficult to find. It seems to be largely the same binary as used by the Iocharger Pedestal charging station, however. The attacker will also need a (low privilege) account to gain access to the  binary, or convince a user with such access to execute a crafted HTTP request.  \n  \nImpact: Critical \u2013 The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete files and services.  \n  \nCVSS clarification:\u00a0Any network connection serving the web interface is vulnerable (AV:N) and there are no additional measures to circumvent (AC:L) nor does the attack require special conditions to be present (AT:N). The attack requires authentication, but the level does not matter (PR:L), nor is user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H) and a compromised device can be used to potentially \"pivot\" into a network that should nopt be reachable (SC:L/SI:L/SA:H). Because this is an EV charger handing significant power, there is a potential safety impact (S:P). THe attack can be autometed (AU:Y). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-09T10:14:02.000000Z"}, {"uuid": "6b826633-1b81-4a8c-b487-dfb5f8ad81ac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43654", "type": "seen", "source": "https://t.me/cvedetector/14813", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43654 - Iocharger AC EV Charger Command Injection\", \n  \"Content\": \"CVE ID : CVE-2024-43654 \nPublished : Jan. 9, 2025, 8:15 a.m. | 40\u00a0minutes ago \nDescription : Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Iocharger  firmware for AC models allows OS Command Injection as root  \nThis issue affects all Iocharger AC EV charger models on a firmware version before 25010801.  \n  \nLikelihood: Moderate \u2013 The  binary does not seem to be used by the web interface, so it might be more difficult to find. It seems to be largely the same binary as used by the Iocharger Pedestal charging station, however. The attacker will also need a (low privilege) account to gain access to the  binary, or convince a user with such access to execute a crafted HTTP request.  \n  \nImpact: Critical \u2013 The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete  \nfiles and services.  \n  \nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-09T10:13:59.000000Z"}, {"uuid": "0a2af82d-eda6-4c16-a155-5dbf0fcadefe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43657", "type": "seen", "source": "https://t.me/cvedetector/14811", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43657 - Iocharger AC Charger Root Command Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-43657 \nPublished : Jan. 9, 2025, 8:15 a.m. | 40\u00a0minutes ago \nDescription : Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root  \n  \nThis issue affects Iocharger firmware for AC model chargers before version 24120701.  \n  \nLikelihood: High. However, the attacker will need a (low privilege) account to gain access to the action.exe CGI binary and upload the crafted firmware file, or convince a user with such access to upload it.  \n  \nImpact: Critical \u2013 The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and deletefiles and services.  \n  \nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-09T10:13:57.000000Z"}, {"uuid": "99647dd9-a693-4121-87cd-f191b0331ffb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43656", "type": "seen", "source": "https://t.me/cvedetector/14810", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43656 - Iocharger AC Model Charger Command Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-43656 \nPublished : Jan. 9, 2025, 8:15 a.m. | 40\u00a0minutes ago \nDescription : Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root  \n  \nThis issue affects Iocharger firmware for AC model chargers before version 24120701.  \n  \nLikelihood: Moderate \u2013 It might be difficult for an attacker to identify the file structure of the  directory, and then modify the backup to add a new CGI script in the correct directory. Furthermore, the attacker will need an account to restore the settings backup, or convince a user with such access to upload a modified backup file.  \n  \nImpact: Critical \u2013 The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and deletefiles and services.  \n  \nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-09T10:13:56.000000Z"}, {"uuid": "fac8044f-2405-414d-bb90-f403a6b0482d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43653", "type": "seen", "source": "https://t.me/cvedetector/14818", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43653 - \"Iocharger AC Charger Command Injection Root Privilege Escalation\"\", \n  \"Content\": \"CVE ID : CVE-2024-43653 \nPublished : Jan. 9, 2025, 8:15 a.m. | 40\u00a0minutes ago \nDescription : Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability\u00a0 allows OS Command Injection as root  \nThis issue affects Iocharger firmware for AC model chargers before version 24120701.  \n  \nLikelihood: Moderate \u2013 The  binary does not seem to be used by the web interface, so it might be more difficult to find. It seems to be largely the same binary as used by the Iocharger Pedestal charging station, however. The attacker will also need a (low privilege) account to gain access to the  binary, or convince a user with such access to execute a crafted HTTP request.  \n  \nImpact: Critical \u2013 The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete  \nfiles and services.  \n  \nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-09T10:14:04.000000Z"}, {"uuid": "bb5b318a-9e1d-4b4f-8224-f25741a8bade", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43659", "type": "seen", "source": "https://t.me/cvedetector/14804", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43659 - \"Iocharger AC Model Firmware Default Credentials Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-43659 \nPublished : Jan. 9, 2025, 8:15 a.m. | 40\u00a0minutes ago \nDescription : After gaining access to the firmware of a charging station, a file at  can be accessed to obtain default credentials that are the same across all Iocharger AC model EV chargers.  \n  \nThis issue affects Iocharger firmware for AC models before firmware version 25010801.   \n  \nThe issue is addressed by requiring a mandatory password change on first login, it is still recommended to change the password on older models.  \n  \nLikelihood: Moderate \u2013 The attacker will first have to abuse a code execution or file inclusion vulnerability (for example by using .sh) to gain access to the .json file, or obtain a firmware dump of the charging station or obtain the firmware via other channels.  \n  \nImpact: Critical \u2013 All chargers using Iocharger firmware for AC models started with the same initial password. For models with firmware version before 25010801 a password change was not mandatory. It is therefore very likely that this firmware password is still active on many chargers. These credentials could, once obtained, allow an attacker to log into many Iocharger charging station, and allow them to execute arbitrary commands via the System \u2192 Custom page.  \n  \nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, and requires high privileges (PR:H), there is no user interaction required (UI:N). The attack leads to a compromised of the confidentialy of the \"super user\" credentials of the device (VC:H/VI:N/VA:N), and can subsequently be used to full compromise and other devices (SC:H/SI:H/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-09T10:13:46.000000Z"}, {"uuid": "aaac73cf-a1b0-466d-ab2c-b0460eb3e3fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43650", "type": "seen", "source": "https://t.me/cvedetector/14815", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43650 - \"Command Injection Vulnerability in Iocharger AC Firmware\"\", \n  \"Content\": \"CVE ID : CVE-2024-43650 \nPublished : Jan. 9, 2025, 8:15 a.m. | 40\u00a0minutes ago \nDescription : Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Iocharger firmware for AC models allows OS Command Injection as root  \n  \nThis issue affects\u00a0 firmware versions before 24120701.  \n  \nLikelihood: Moderate \u2013 The  binary does not seem to be used by the web interface, so it might be more difficult to find. It seems to be largely the same binary as used by the Iocharger Pedestal charging station, however. The attacker will also need a (low privilege) account to gain access to the  binary, or convince a user with such access to execute a crafted HTTP request.  \n  \nImpact: Critical \u2013 The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete  \nfiles and services.  \n  \nCVSS clarification: The attack can be executed over any network connection serving the web interface (AV:N). There are no additional measures that need to be circumvented (AC:L) or attack preconditions (AT:N). THe attack is privileged, but the level does not matter (PR:L) and does not require user interaction (UI:N). Attack leads to full system compromised (VC:H/VI:H/VA:H) and compromised devices can be used to \"pivot\" to other networks that should be unreachable (SC:L/SI:L/SA:H). Because this an EV charger using high power, there is a potential safety impact (S:P). The attack can be automated (AU:Y). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-09T10:14:01.000000Z"}, {"uuid": "753fcdaa-5d12-4b01-83a7-c6236377d0f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43658", "type": "seen", "source": "https://t.me/cvedetector/14812", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43658 - Iocharger Home File Traversal and Deletion Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-43658 \nPublished : Jan. 9, 2025, 8:15 a.m. | 40\u00a0minutes ago \nDescription : Patch traversal, External Control of File Name or Path vulnerability in  Iocharger Home allows deletion of arbitrary files  \nThis issue affects Iocharger firmware for AC model before firmware version 25010801.  \n  \nLikelihood: High, but requires authentication  \n  \nImpact: Critical \u2013 The vulnerability can be used to delete any file on the charging station, severely impacting the integrity of the charging station. Furthermore, the vulnerability could be used to delete binaries required for the functioning of the charging station, severely impacting the availability of the charging station.  \n  \nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads compromised of the integrity and availability of the device (VVC:N/VI:H/VA:H), with no effect on subsequent systems (SC:N/SI:N/SA:N). We do not forsee a safety impact (S:N). This attack can be automated (AU:Y). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-09T10:13:58.000000Z"}, {"uuid": "8594bc6e-a5f8-4c38-a5cf-0f8ce483bf9a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43655", "type": "seen", "source": "https://t.me/cvedetector/14809", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43655 - Iocharger AC Charger Root Command Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-43655 \nPublished : Jan. 9, 2025, 8:15 a.m. | 40\u00a0minutes ago \nDescription : Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root  \n  \nThis issue affects Iocharger firmware for AC model chargers before version 24120701.  \n  \nLikelihood: Moderate \u2013 The attacker will first need to find the name of the script, and needs a (low privilege) account to gain access to the script, or convince a user with such access to execute a request to it.  \n  \nImpact: Critical \u2013 The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and deletefiles and services.  \n  \nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-09T10:13:53.000000Z"}, {"uuid": "83578d35-74b4-4004-bd91-c64662323096", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43652", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113797409863565060", "content": "", "creation_timestamp": "2025-01-09T08:17:53.466270Z"}, {"uuid": "73bbc58c-aaf7-4902-8a91-6e7f7f48e47e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43655", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113797409910755927", "content": "", "creation_timestamp": "2025-01-09T08:17:54.328502Z"}, {"uuid": "5f3b668f-455f-4c1f-b8f5-c879226a9951", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43654", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113797409895021271", "content": "", "creation_timestamp": "2025-01-09T08:17:54.432771Z"}, {"uuid": "5af7949c-56cd-4e01-80b1-0793fa5b72bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43653", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113797409879259586", "content": "", "creation_timestamp": "2025-01-09T08:17:54.636990Z"}, {"uuid": "f7425524-42b4-458e-9935-3fe55631935c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43657", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113797468926541396", "content": "", "creation_timestamp": "2025-01-09T08:32:54.693584Z"}, {"uuid": "c1c2552c-e1fe-4bde-a890-e7c0678e9ba7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43656", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113797468909077158", "content": "", "creation_timestamp": "2025-01-09T08:32:54.895274Z"}, {"uuid": "ce1dd634-8860-4586-a2ca-762f78328ebc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43659", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113797468958090657", "content": "", "creation_timestamp": "2025-01-09T08:32:55.135418Z"}, {"uuid": "787e0666-9528-4e59-80bf-14c7ea281bfe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43658", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113797468942476103", "content": "", "creation_timestamp": "2025-01-09T08:32:55.960779Z"}, {"uuid": "147e676f-6ea9-47a4-aa96-ad4be198cdc1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43650", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/113799007314543960", "content": "", "creation_timestamp": "2025-01-09T15:04:08.754880Z"}, {"uuid": "71365cd2-3c80-4e59-87ba-0dee91914c84", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43651", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/113799007314543960", "content": "", "creation_timestamp": "2025-01-09T15:04:08.786811Z"}, {"uuid": "ec7d6198-31a0-4905-ad38-26ca290ff028", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43652", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/113799007314543960", "content": "", "creation_timestamp": "2025-01-09T15:04:08.820461Z"}, {"uuid": "6ea8bd07-ad49-491d-a22e-01edf05ea667", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43653", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/113799007314543960", "content": "", "creation_timestamp": "2025-01-09T15:04:08.852585Z"}, {"uuid": "9b48b7d5-fcc8-4bb7-ae20-11a5d5d6529f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43654", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/113799007314543960", "content": "", "creation_timestamp": "2025-01-09T15:04:08.886945Z"}, {"uuid": "91ebb0c8-76cd-491f-bb28-507662ae8a0a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43655", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/113799007314543960", "content": "", "creation_timestamp": "2025-01-09T15:04:08.921777Z"}, {"uuid": "3a2b670c-86ba-49e2-b06d-35ba6d565c8f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43656", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/113799007314543960", "content": "", "creation_timestamp": "2025-01-09T15:04:08.954557Z"}, {"uuid": "b0e861a3-b097-489c-aafe-0bbe89789c66", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43657", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/113799007314543960", "content": "", "creation_timestamp": "2025-01-09T15:04:08.989474Z"}, {"uuid": "dcadbf74-6ec3-45e2-8808-7ec538013317", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43658", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/113799007314543960", "content": "", "creation_timestamp": "2025-01-09T15:04:09.023266Z"}, {"uuid": "a7de4fcc-46e4-46ae-9cd3-3c3e67d7ab48", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43659", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/113799007314543960", "content": "", "creation_timestamp": "2025-01-09T15:04:09.054877Z"}, {"uuid": "84deccd2-415f-4af4-87bb-1f26f634601d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43650", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113797350844757560", "content": "", "creation_timestamp": "2025-01-09T08:02:53.131383Z"}, {"uuid": "e1104d00-f960-4249-aa9c-ac3361cf8668", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43651", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113797350858864367", "content": "", "creation_timestamp": "2025-01-09T08:02:53.431831Z"}, {"uuid": "5d68fc2e-1247-4547-b4f4-aaf21b726d85", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43653", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/113799182324384853", "content": "", "creation_timestamp": "2025-01-09T15:48:39.321998Z"}, {"uuid": "f1011189-83ed-4751-b917-072efd2df26a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43657", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/113799182525499745", "content": "", "creation_timestamp": "2025-01-09T15:48:42.422565Z"}, {"uuid": "cd4c6df0-ea84-496b-9d53-6ee08d01807e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43658", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lfcfb52uhy2h", "content": "", "creation_timestamp": "2025-01-09T09:43:08.473842Z"}, {"uuid": "069fef21-7a3c-4d41-84bc-726ba4a3af30", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43655", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/914", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-43655\n\ud83d\udd39 Description: Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root\n\nThis issue affects Iocharger firmware for AC model chargers before version 24120701.\n\nLikelihood: Moderate \u2013 The attacker will first need to find the name of the script, and needs a (low privilege) account to gain access to the script, or convince a user with such access to execute a request to it.\n\nImpact: Critical \u2013 The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and deletefiles and services.\n\nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y).\n\ud83d\udccf Published: 2025-01-09T07:56:45.279Z\n\ud83d\udccf Modified: 2025-01-09T07:56:45.279Z\n\ud83d\udd17 References:\n1. https://csirt.divd.nl/DIVD-2024-00035/\n2. https://csirt.divd.nl/CVE-2024-43655/\n3. https://iocharger.com", "creation_timestamp": "2025-01-09T08:17:12.000000Z"}, {"uuid": "007cf810-08ac-44ef-869f-7a577aa6ff19", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43657", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/912", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-43657\n\ud83d\udd39 Description: Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root\n\nThis issue affects Iocharger firmware for AC model chargers before version 24120701.\n\nLikelihood: High. However, the attacker will need a (low privilege) account to gain access to the action.exe CGI binary and upload the crafted firmware file, or convince a user with such access to upload it.\n\nImpact: Critical \u2013 The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and deletefiles and services.\n\nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y).\n\ud83d\udccf Published: 2025-01-09T07:56:46.268Z\n\ud83d\udccf Modified: 2025-01-09T07:56:46.268Z\n\ud83d\udd17 References:\n1. https://csirt.divd.nl/DIVD-2024-00035/\n2. https://csirt.divd.nl/CVE-2024-43657/\n3. https://iocharger.com", "creation_timestamp": "2025-01-09T08:16:24.000000Z"}, {"uuid": "47bfd74f-1365-40f5-9b5d-b28ae6b2fa65", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43658", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/911", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-43658\n\ud83d\udd39 Description: Patch traversal, External Control of File Name or Path vulnerability in  Iocharger Home allows deletion of arbitrary files\nThis issue affects Iocharger firmware for AC model before firmware version 25010801.\n\nLikelihood: High, but requires authentication\n\nImpact: Critical \u2013 The vulnerability can be used to delete any file on the charging station, severely impacting the integrity of the charging station. Furthermore, the vulnerability could be used to delete binaries required for the functioning of the charging station, severely impacting the availability of the charging station.\n\nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads compromised of the integrity and availability of the device (VVC:N/VI:H/VA:H), with no effect on subsequent systems (SC:N/SI:N/SA:N). We do not forsee a safety impact (S:N). This attack can be automated (AU:Y).\n\ud83d\udccf Published: 2025-01-09T07:56:47.273Z\n\ud83d\udccf Modified: 2025-01-09T07:56:47.273Z\n\ud83d\udd17 References:\n1. https://csirt.divd.nl/DIVD-2024-00035/\n2. https://csirt.divd.nl/CVE-2024-43658/\n3. https://iocharger.com", "creation_timestamp": "2025-01-09T08:15:45.000000Z"}, {"uuid": "88b23237-8d69-4b9f-8ad4-c3e3cc784761", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43658", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfcagqdsll22", "content": "", "creation_timestamp": "2025-01-09T08:16:47.354728Z"}, {"uuid": "3a737a01-3f3a-4eb7-afcd-9cfaece72b33", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43650", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfcafxpgze2d", "content": "", "creation_timestamp": "2025-01-09T08:16:21.788255Z"}, {"uuid": "6a99ff93-9dcc-49ca-9d89-b5c834c4a264", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43651", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfcag34pmy25", "content": "", "creation_timestamp": "2025-01-09T08:16:25.685623Z"}, {"uuid": "28723d36-9956-4c5f-96d6-21501dc7d3f3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43652", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfcag6ire22k", "content": "", "creation_timestamp": "2025-01-09T08:16:29.091131Z"}, {"uuid": "6cdb6c9c-0481-49a7-880d-cc192cc26723", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43653", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfcagbh36p2l", "content": "", "creation_timestamp": "2025-01-09T08:16:32.184640Z"}, {"uuid": "5a0798c9-acd9-4c2e-b371-5477d5a67aaf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43655", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfcaggilxz2x", "content": "", "creation_timestamp": "2025-01-09T08:16:37.067924Z"}, {"uuid": "1176bc60-390f-4bf9-a485-b59aadb15af8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43656", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfcagk2tgq25", "content": "", "creation_timestamp": "2025-01-09T08:16:40.848639Z"}, {"uuid": "6573ea30-24b3-4533-99a8-0db1cc23467b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43656", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/113799182469744568", "content": "", "creation_timestamp": "2025-01-09T15:48:41.670632Z"}, {"uuid": "9efd78ec-6a66-41b5-9846-b448ecb6d06c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43657", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfcagnja4m2d", "content": "", "creation_timestamp": "2025-01-09T08:16:44.460184Z"}, {"uuid": "26e1f3fa-df22-4b06-b156-3ecb40794831", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43652", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/113799182284548375", "content": "", "creation_timestamp": "2025-01-09T15:48:38.555027Z"}, {"uuid": "2282140c-c184-4a38-a21d-6a8227582c06", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43654", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/113799182402176187", "content": "", "creation_timestamp": "2025-01-09T15:48:40.556342Z"}, {"uuid": "8c173293-0233-4efa-a925-9e5e40f94002", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43659", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfcagsjtsy25", "content": "", "creation_timestamp": "2025-01-09T08:16:49.846207Z"}, {"uuid": "7717beab-9866-4bcb-99b0-1959e9a4bd60", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43655", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/7141", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-43655\n\ud83d\udd25 CVSS Score: 9.3 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:H/S:P/AU:Y)\n\ud83d\udd39 Description: Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root\n\nThis issue affects Iocharger firmware for AC model chargers before version 24120701.\n\nLikelihood: Moderate \u2013 The attacker will first need to find the name of the script, and needs a (low privilege) account to gain access to the script, or convince a user with such access to execute a request to it.\n\nImpact: Critical \u2013 The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and deletefiles and services.\n\nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y).\n\ud83d\udccf Published: 2025-01-09T07:56:45.279Z\n\ud83d\udccf Modified: 2025-03-11T13:07:19.985Z\n\ud83d\udd17 References:\n1. https://csirt.divd.nl/DIVD-2024-00035/\n2. https://csirt.divd.nl/CVE-2024-43655/\n3. https://iocharger.com", "creation_timestamp": "2025-03-11T13:40:02.000000Z"}]}