{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-18825 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-18825 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-18825 is a high-severity vulnerability in n/a, published on 17 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-18825 and fix it if it is affected.\n\nWhat it is: CVE-2019-18825 is a high-severity vulnerability in n/a, published on 17 Dec 2019. 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-2019-18825 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-2019-18825/ (Markdown: https://insights.sbomify.com/CVE-2019-18825/index.md)","id":"CVE-2019-18825","markdown":"https://insights.sbomify.com/CVE-2019-18825/index.md","name":"CVE-2019-18825","record":{"aliases":["GHSA-fvrj-qh22-gh9g"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ClickShare Base Unit","requires_auth":"none","summary":"Attackers can decrypt data on Barco ClickShare devices because encryption keys are shared across all units, compromising data confidentiality.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"clickshare_cs-100_huddle_firmware","vendor":"barco"},{"product":"clickshare_cse-200_firmware","vendor":"barco"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"Barco ClickShare Huddle CS-100 devices before 1.9.0 and CSE-200 devices before 1.9.0 have incorrect Credentials Management. The ClickShare Base Unit implements encryption at rest using encryption keys which are shared across all ClickShare Base Units of models CS-100 \u0026 CSE-200.","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-2019-18825","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2019-18826"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2019-18824"},"products":["n/a"],"published":"2019-12-17","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can decrypt data on Barco ClickShare devices because encryption keys are shared across all units, compromising data confidentiality.","url":"https://insights.sbomify.com/CVE-2019-18825/"}