{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-11624 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-11624 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-11624 is a critical vulnerability in n/a, published on 23 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-11624 and fix it if it is affected.\n\nWhat it is: CVE-2020-11624 is a critical vulnerability in n/a, published on 23 Jul 2020. 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-2020-11624 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-2020-11624/ (Markdown: https://insights.sbomify.com/CVE-2020-11624/index.md)","id":"CVE-2020-11624","markdown":"https://insights.sbomify.com/CVE-2020-11624/index.md","name":"CVE-2020-11624","record":{"aliases":["GHSA-qfr6-gxpj-wr4q"],"analysis":{"component_type":"iot_embedded","fix_type":"configuration_change","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IP security camera","requires_auth":"none","summary":"Attackers can access AvertX IP cameras using default admin credentials because password changes are not enforced and usernames are exposed.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hd438_firmware","vendor":"avertx"},{"product":"hd838_firmware","vendor":"avertx"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","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-521","name":"Weak Password Requirements"}],"description":"An issue was discovered in AvertX Auto focus Night Vision HD Indoor/Outdoor IP Dome Camera HD838 and Night Vision HD Indoor/Outdoor Mini IP Bullet Camera HD438. They do not require users to change the default password for the admin account. They only show a pop-up window suggesting a change but there's no enforcement. An administrator can click Cancel and proceed to use the device without changing the password. Additionally, they disclose the default username within the login.js script. Since many attacks for IoT devices, including malware and exploits, are based on the usage of default credentials, it makes these cameras an easy target for malicious actors.","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-2020-11624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-11625"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2020-11623"},"products":["n/a"],"published":"2020-07-23","related":[{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2020-11623","kev_date_added":null,"published":"2020-07-23"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2020-11625","kev_date_added":null,"published":"2020-07-23"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can access AvertX IP cameras using default admin credentials because password changes are not enforced and usernames are exposed.","url":"https://insights.sbomify.com/CVE-2020-11624/"}