{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-6825 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-6825 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-6825 is a critical vulnerability in n/a, published on 9 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-6825 and fix it if it is affected.\n\nWhat it is: CVE-2018-6825 is a critical vulnerability in n/a, published on 9 Feb 2018. 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-2018-6825 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-2018-6825/ (Markdown: https://insights.sbomify.com/CVE-2018-6825/index.md)","id":"CVE-2018-6825","markdown":"https://insights.sbomify.com/CVE-2018-6825/index.md","name":"CVE-2018-6825","record":{"aliases":["GHSA-jhr3-x436-3q9g"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"VOBOT CLOCK","requires_auth":"none","summary":"Attackers can gain root access via hardcoded SSH credentials on VOBOT CLOCK devices, requiring an upgrade to secure the system.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vobot_firmware","vendor":"omninova"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered on VOBOT CLOCK before 0.99.30 devices. An SSH server exists with a hardcoded vobot account that has root access.","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-2018-6825","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in n/a","id":"CVE-2018-6826"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-6824"},"products":["n/a"],"published":"2018-02-09","related":[{"cvss_score":8.1,"headline":"Weak cryptography in n/a","id":"CVE-2018-6827","kev_date_added":null,"published":"2018-02-09"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2018-6826","kev_date_added":null,"published":"2018-02-09"}],"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-05","vendors":["n/a"]},"summary":"Attackers can gain root access via hardcoded SSH credentials on VOBOT CLOCK devices, requiring an upgrade to secure the system.","url":"https://insights.sbomify.com/CVE-2018-6825/"}