{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-33372 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-33372 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-33372 is a critical vulnerability in n/a, published on 4 Aug 2023. 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-33372 and fix it if it is affected.\n\nWhat it is: CVE-2023-33372 is a critical vulnerability in n/a, published on 4 Aug 2023. 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-33372 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-33372/ (Markdown: https://insights.sbomify.com/CVE-2023-33372/index.md)","id":"CVE-2023-33372","markdown":"https://insights.sbomify.com/CVE-2023-33372/index.md","name":"CVE-2023-33372","record":{"aliases":["GHSA-vvv6-p6rr-p76r"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Connected IO device","requires_auth":"none","summary":"Hardcoded credentials in Connected IO firmware allow attackers to bypass authentication and impersonate devices on the MQTT broker.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"connected_io","vendor":"connectedio"}],"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-798","name":"Use of Hard-coded Credentials"}],"description":"Connected IO v2.1.0 and prior uses a hard-coded username/password pair embedded in their device's firmware used for device communication using MQTT. An attacker who gained access to these credentials is able to connect to the MQTT broker and send messages on behalf of devices, impersonating them. in order to sign and verify JWT session tokens, allowing attackers to sign arbitrary session tokens and bypass authentication.","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-33372","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2023-33373"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2023-33371"},"products":["n/a"],"published":"2023-08-04","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-33373","kev_date_added":null,"published":"2023-08-04"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-33374","kev_date_added":null,"published":"2023-08-04"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-33375","kev_date_added":null,"published":"2023-08-04"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-33376","kev_date_added":null,"published":"2023-08-04"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-33377","kev_date_added":null,"published":"2023-08-04"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-33378","kev_date_added":null,"published":"2023-08-04"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-17","vendors":["n/a"]},"summary":"Hardcoded credentials in Connected IO firmware allow attackers to bypass authentication and impersonate devices on the MQTT broker.","url":"https://insights.sbomify.com/CVE-2023-33372/"}