{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48539 exists.","fix":"No fix has been published for CVE-2024-48539 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-48539 is a critical vulnerability in n/a, published on 24 Oct 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-48539 and fix it if it is affected.\n\nWhat it is: CVE-2024-48539 is a critical vulnerability in n/a, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48539 exists.\n\nAffected product: n/a. 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-48539/ (Markdown: https://insights.sbomify.com/CVE-2024-48539/index.md)","id":"CVE-2024-48539","markdown":"https://insights.sbomify.com/CVE-2024-48539/index.md","name":"CVE-2024-48539","record":{"aliases":["GHSA-c844-5xj7-6j82"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["security_bypass","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Neye3C firmware","requires_auth":"none","summary":"Hardcoded encryption key in Neye3C firmware allows attackers to bypass security controls and potentially execute code during updates.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Neye3C v4.5.2.0 was discovered to contain a hardcoded encryption key in the firmware update mechanism.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2024-48539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2024-48540"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2024-48538"},"products":["n/a"],"published":"2024-10-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Hardcoded encryption key in Neye3C firmware allows attackers to bypass security controls and potentially execute code during updates.","url":"https://insights.sbomify.com/CVE-2024-48539/"}