{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-0038 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-0038 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-0038 is a critical vulnerability in n/a, published on 11 Jul 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-0038 and fix it if it is affected.\n\nWhat it is: CVE-2018-0038 is a critical vulnerability in n/a, published on 11 Jul 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-0038 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-0038/ (Markdown: https://insights.sbomify.com/CVE-2018-0038/index.md)","id":"CVE-2018-0038","markdown":"https://insights.sbomify.com/CVE-2018-0038/index.md","name":"CVE-2018-0038","record":{"aliases":["GHSA-fhqp-r39f-9w65"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Contrail Service Orchestration","requires_auth":"none","summary":"Attackers can access sensitive data in Cassandra due to hardcoded credentials enabled by default in Juniper Contrail Service Orchestration.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[{"product":"contrail_service_orchestration","vendor":"juniper"}],"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":"Juniper Networks Contrail Service Orchestration releases prior to 3.3.0 have Cassandra service enabled by default with hardcoded credentials. These credentials allow network based attackers unauthorized access to information stored in Cassandra.","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-0038","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":"Contrail Service Orchestration: Hardcoded credentials for Grafana service","id":"CVE-2018-0039"},"packages":[],"prev":{"headline":"Junos OS: RPD daemon crashes due to receipt of crafted BGP NOTIFICATION messages","id":"CVE-2018-0037"},"products":["n/a"],"published":"2018-07-11","related":[{"cvss_score":9.8,"headline":"Contrail Service Orchestration: hardcoded cryptographic certificates and keys","id":"CVE-2018-0040","kev_date_added":null,"published":"2018-07-11"},{"cvss_score":9.8,"headline":"Contrail Service Orchestration: Hardcoded credentials for Keystone service.","id":"CVE-2018-0041","kev_date_added":null,"published":"2018-07-11"},{"cvss_score":9.8,"headline":"Juniper Networks CSO versions prior to 4.0.0 may log passwords in log files leading to an information disclosure vulnerability.","id":"CVE-2018-0042","kev_date_added":null,"published":"2018-07-11"},{"cvss_score":7.7,"headline":"Contrail Service Orchestration: Tenants able to see other tenants policies via REST API interface","id":"CVE-2022-22152","kev_date_added":null,"published":"2022-01-19"},{"cvss_score":7.3,"headline":"Privilege escalation in Contrail Service Orchestration","id":"CVE-2022-22189","kev_date_added":null,"published":"2022-04-14"},{"cvss_score":6.5,"headline":"Contrail Service Orchestration: Hardcoded credentials for Grafana service","id":"CVE-2018-0039","kev_date_added":null,"published":"2018-07-11"}],"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 access sensitive data in Cassandra due to hardcoded credentials enabled by default in Juniper Contrail Service Orchestration.","url":"https://insights.sbomify.com/CVE-2018-0038/"}