{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-41611 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-41611 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-41611 is a medium-severity vulnerability in n/a, published on 18 Sep 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-2023-41611 and fix it if it is affected.\n\nWhat it is: CVE-2023-41611 is a medium-severity vulnerability in n/a, published on 18 Sep 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-2023-41611 in the wild and no public exploit code.\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-2023-41611/ (Markdown: https://insights.sbomify.com/CVE-2023-41611/index.md)","id":"CVE-2023-41611","markdown":"https://insights.sbomify.com/CVE-2023-41611/index.md","name":"CVE-2023-41611","record":{"aliases":["GHSA-2p9x-h657-5mg3"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Victure PC420 camera","requires_auth":"none","summary":"Attackers can decrypt data using a weak, partially hardcoded key in the Victure PC420 camera firmware.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pc420_firmware","vendor":"govicture"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Victure PC420 1.1.39 was discovered to use a weak and partially hardcoded key to encrypt data.","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":"Hardcoded credentials in n/a","id":"CVE-2023-41611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2023-41612"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2023-41610"},"products":["n/a"],"published":"2024-09-18","related":[{"cvss_score":9.6,"headline":"Stack-based buffer overflow leading to RCE in Victure Camera","id":"CVE-2020-15744","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":8.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-41610","kev_date_added":null,"published":"2024-09-18"},{"cvss_score":8.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-41612","kev_date_added":null,"published":"2024-09-18"}],"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":"2024-11-21","vendors":["n/a"]},"summary":"Attackers can decrypt data using a weak, partially hardcoded key in the Victure PC420 camera firmware.","url":"https://insights.sbomify.com/CVE-2023-41611/"}