{"answers":{"affected":"2 open source packages ship an affected version, including org.springframework.credhub:spring-credhub-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-15795 in the wild and no public exploit code.","fix":"Upgrade org.springframework.credhub:spring-credhub-core to 1.1.0 or later.","what":"CVE-2018-15795 is a high-severity vulnerability in Pivotal Cloud Foundry CredHub Service Broker, published on 13 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-15795 and fix it if it is affected.\n\nWhat it is: CVE-2018-15795 is a high-severity vulnerability in Pivotal Cloud Foundry CredHub Service Broker, published on 13 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-15795 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework.credhub:spring-credhub-core (Maven): affected all versions; fixed in 1.1.0\n- org.springframework.credhub:spring-credhub-core (Maven): affected all versions; fixed in 1.1.0\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-15795/ (Markdown: https://insights.sbomify.com/CVE-2018-15795/index.md)","id":"CVE-2018-15795","markdown":"https://insights.sbomify.com/CVE-2018-15795/index.md","name":"CVE-2018-15795","record":{"aliases":["GHSA-q3jg-4c82-j4xh"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CredHub Service Broker","requires_auth":"high_privilege","summary":"Attackers can guess the service broker's client secret to obtain or modify user credentials in Pivotal CredHub Service Broker.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"credhub_service_broker","vendor":"pivotal_software"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"Pivotal CredHub Service Broker, versions prior to 1.1.0, uses a guessable form of random number generation in creating service broker's UAA client. A remote malicious user may guess the client secret and obtain or modify credentials for users of the CredHub Service.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"CredHub Service Broker uses guessable client secret","id":"CVE-2018-15795","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"weak_cryptography","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Signing Key Extraction in Bits Service Release","id":"CVE-2018-15796"},"packages":[{"ecosystem":"Maven","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"org.springframework.credhub:spring-credhub-core","purl":null,"source":"GHSA-q3jg-4c82-j4xh"},{"ecosystem":"Maven","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"org.springframework.credhub:spring-credhub-core","purl":"pkg:maven/org.springframework.credhub/spring-credhub-core","source":"GHSA-q3jg-4c82-j4xh"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2018-15794"},"products":["CredHub Service Broker"],"published":"2018-11-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-09-16","vendors":["Pivotal Cloud Foundry"]},"summary":"Attackers can guess the service broker's client secret to obtain or modify user credentials in Pivotal CredHub Service Broker.","url":"https://insights.sbomify.com/CVE-2018-15795/"}