{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-7306 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-7306 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-7306 is a medium-severity vulnerability in n/a, published on 4 Apr 2017. 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-2017-7306 and fix it if it is affected.\n\nWhat it is: CVE-2017-7306 is a medium-severity vulnerability in n/a, published on 4 Apr 2017. 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-2017-7306 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-2017-7306/ (Markdown: https://insights.sbomify.com/CVE-2017-7306/index.md)","id":"CVE-2017-7306","markdown":"https://insights.sbomify.com/CVE-2017-7306/index.md","name":"CVE-2017-7306","record":{"aliases":["GHSA-hfgj-gwp8-p5ph"],"analysis":{"component_type":"network_device","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Riverbed RiOS appliance","requires_auth":"none","summary":"Attackers can bypass secure vault protection using a weak default password derived from the serial number, requiring physical proximity.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rios","vendor":"riverbed"}],"cvss":{"score":6.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-521","name":"Weak Password Requirements"}],"description":"Riverbed RiOS through 9.6.0 has a weak default password for the secure vault, which makes it easier for physically proximate attackers to defeat the secure-vault protection mechanism by leveraging knowledge of the password algorithm and the appliance serial number. NOTE: the vendor believes that this does not meet the definition of a vulnerability. The product contains correct computational logic for supporting arbitrary password changes by customers; however, a password change is optional to meet different customers' needs","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-2017-7306","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2017-7307"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2017-7305"},"products":["n/a"],"published":"2017-04-04","related":[{"cvss_score":6.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-7307","kev_date_added":null,"published":"2017-04-04"},{"cvss_score":4.6,"headline":"Information disclosure in n/a","id":"CVE-2017-5670","kev_date_added":null,"published":"2017-04-04"},{"cvss_score":4.6,"headline":"Security feature bypass in n/a","id":"CVE-2017-7305","kev_date_added":null,"published":"2017-04-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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass secure vault protection using a weak default password derived from the serial number, requiring physical proximity.","url":"https://insights.sbomify.com/CVE-2017-7306/"}