{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-3373 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-3373 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-3373 is a medium-severity vulnerability in n/a, published on 21 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-3373 and fix it if it is affected.\n\nWhat it is: CVE-2015-3373 is a medium-severity vulnerability in n/a, published on 21 Apr 2015. 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-2015-3373 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-2015-3373/ (Markdown: https://insights.sbomify.com/CVE-2015-3373/index.md)","id":"CVE-2015-3373","markdown":"https://insights.sbomify.com/CVE-2015-3373/index.md","name":"CVE-2015-3373","record":{"aliases":["GHSA-3hxp-x9v3-rrq4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Drupal AWS module","requires_auth":"none","summary":"Remote attackers can guess access tokens to create backups due to weak token generation in the Drupal AWS module.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"amazon_aws","vendor":"amazon_aws_project"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Amazon AWS module before 7.x-1.3 for Drupal uses the base URL and AWS access key to generate the access token, which makes it easier for remote attackers to guess the token value and create backups via a crafted URL.","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":"Information disclosure in n/a","id":"CVE-2015-3373","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2015"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2015-3374"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2015-3372"},"products":["n/a"],"published":"2015-04-21","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":"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-06","vendors":["n/a"]},"summary":"Remote attackers can guess access tokens to create backups due to weak token generation in the Drupal AWS module.","url":"https://insights.sbomify.com/CVE-2015-3373/"}