{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-12907 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-12907 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-12907 is a high-severity server-side request forgery vulnerability in n/a, published on 27 Jun 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-12907 and fix it if it is affected.\n\nWhat it is: CVE-2018-12907 is a high-severity server-side request forgery vulnerability in n/a, published on 27 Jun 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-12907 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-12907/ (Markdown: https://insights.sbomify.com/CVE-2018-12907/index.md)","id":"CVE-2018-12907","markdown":"https://insights.sbomify.com/CVE-2018-12907/index.md","name":"CVE-2018-12907","record":{"aliases":["GHSA-583j-w294-52g8"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Cloud storage sync tool","requires_auth":"none","summary":"Attackers can trigger transmission of arbitrary URL content to Google Cloud Storage via unvalidated URL fields in Rclone sync operations.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rclone","vendor":"rclone"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Rclone 1.42, use of \"rclone sync\" to migrate data between two Google Cloud Storage buckets might allow attackers to trigger the transmission of any URL's content to Google, because there is no validation of a URL field received from the Google Cloud Storage API server, aka a \"RESTLESS\" issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Server-side request forgery in n/a","id":"CVE-2018-12907","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-12908"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-12905"},"products":["n/a"],"published":"2018-06-27","related":[{"cvss_score":9.8,"headline":"rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass","id":"CVE-2026-88018","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Rclone: Unauthenticated command execution in `rclone rcd --rc-serve` via inline remote instantiation, bypassing CVE-2026-41179 fix","id":"CVE-2026-49980","kev_date_added":null,"published":"2026-06-24"},{"cvss_score":9.2,"headline":"RClone: Unauthenticated operations/fsinfo allows attacker-controlled backend instantiation and local command execution","id":"CVE-2026-41179","kev_date_added":null,"published":"2026-04-23"},{"cvss_score":9.2,"headline":"Rclone: Unauthenticated options/set allows runtime auth bypass, leading to sensitive operations and command execution","id":"CVE-2026-41176","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":8.8,"headline":"rclone `serve restic --private-repos` authorization bypass: `..` in the URL path lets an authenticated user read, overwrite and delete other users' repositories","id":"CVE-2026-59733","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":8.7,"headline":"Rclone before 1.75.2 Path Traversal via serve webdav MKCOL","id":"CVE-2026-116191","kev_date_added":null,"published":"2026-10-25"},{"cvss_score":8.2,"headline":"rclone from 1.37 before 1.74.2 SSRF via --rc-serve scheme-relative remote roots","id":"CVE-2026-116192","kev_date_added":null,"published":"2026-10-25"}],"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 trigger transmission of arbitrary URL content to Google Cloud Storage via unvalidated URL fields in Rclone sync operations.","url":"https://insights.sbomify.com/CVE-2018-12907/"}