{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2024-26000 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-26000 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-26000 is a medium-severity vulnerability in PHOENIX CONTACT CHARX SEC-3000, published on 12 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-26000 and fix it if it is affected.\n\nWhat it is: CVE-2024-26000 is a medium-severity vulnerability in PHOENIX CONTACT CHARX SEC-3000, published on 12 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-26000 in the wild and no public exploit code.\n\nAffected product: PHOENIX CONTACT CHARX SEC-3000. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-26000/ (Markdown: https://insights.sbomify.com/CVE-2024-26000/index.md)","id":"CVE-2024-26000","markdown":"https://insights.sbomify.com/CVE-2024-26000/index.md","name":"CVE-2024-26000","record":{"aliases":["GHSA-3q3p-mxc5-jrmq"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"CHARX SEC charging controller","requires_auth":"none","summary":"Unauthenticated remote attackers can read out-of-bounds memory in the MQTT stack of PHOENIX CONTACT CHARX SEC devices.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERTVDE","cpe":[{"product":"charx_sec-3000_firmware","vendor":"phoenixcontact"},{"product":"charx_sec-3050_firmware","vendor":"phoenixcontact"},{"product":"charx_sec-3100_firmware","vendor":"phoenixcontact"},{"product":"charx_sec-3150_firmware","vendor":"phoenixcontact"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"An unauthenticated remote attacker can read memory out of bounds due to improper input validation in the MQTT stack. The brute force attack is not always successful because of memory randomization.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"PHOENIX CONTACT: Out of bounds read only memory access","id":"CVE-2024-26000","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"PHOENIX CONTACT: Out of bounds write only memory access","id":"CVE-2024-26001"},"packages":[],"prev":{"headline":"PHOENIX CONTACT: Privilege escalation in the OCPP agent service","id":"CVE-2024-25999"},"products":["CHARX SEC-3000","CHARX SEC-3050","CHARX SEC-3100","CHARX SEC-3150"],"published":"2024-03-12","related":[{"cvss_score":9.8,"headline":"Remote Code Execution via Unauthenticated Configuration Manipulation","id":"CVE-2025-25270","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":9.8,"headline":"PHOENIX CONTACT: Remote code execution in CHARX Series","id":"CVE-2024-25995","kev_date_added":null,"published":"2024-03-12"},{"cvss_score":8.8,"headline":"Unauthenticated Configuration Access via Exposed API Endpoint","id":"CVE-2025-25268","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":8.8,"headline":"OCPP Backend Configuration via Insecure Defaults","id":"CVE-2025-25271","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":8.7,"headline":"PHOENIX CONTACT: Lack of SSL support in CHARX Series","id":"CVE-2024-26288","kev_date_added":null,"published":"2024-03-12"},{"cvss_score":8.6,"headline":"Phoenix Contact: update feature from CHARX controller can be used to reset a low privilege user password","id":"CVE-2024-6788","kev_date_added":null,"published":"2024-08-13"},{"cvss_score":8.4,"headline":"Local Privilege Escalation via Unauthenticated Command Injection","id":"CVE-2025-25269","kev_date_added":null,"published":"2025-07-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-16","vendors":["PHOENIX CONTACT"]},"summary":"Unauthenticated remote attackers can read out-of-bounds memory in the MQTT stack of PHOENIX CONTACT CHARX SEC devices.","url":"https://insights.sbomify.com/CVE-2024-26000/"}