# CVE-2018-12907: Server-side request forgery in n/a

> Attackers can trigger transmission of arbitrary URL content to Google Cloud Storage via unvalidated URL fields in Rclone sync operations.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-583j-w294-52g8

## What is CVE-2018-12907?

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.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-12907?

It affects 1 product.


Products: Rclone Rclone.

## How do I fix CVE-2018-12907?

No fix has been published for CVE-2018-12907 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-12907 being exploited?

There is no known exploitation of CVE-2018-12907 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-88018](https://insights.sbomify.com/CVE-2026-88018/): rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass (critical 9.8)
- [CVE-2026-49980](https://insights.sbomify.com/CVE-2026-49980/): Rclone: Unauthenticated command execution in `rclone rcd --rc-serve` via inline remote instantiation, bypassing CVE-2026-41179 fix (critical 9.8)
- [CVE-2026-41179](https://insights.sbomify.com/CVE-2026-41179/): RClone: Unauthenticated operations/fsinfo allows attacker-controlled backend instantiation and local command execution (critical 9.2)
- [CVE-2026-41176](https://insights.sbomify.com/CVE-2026-41176/): Rclone: Unauthenticated options/set allows runtime auth bypass, leading to sensitive operations and command execution (critical 9.2)
- [CVE-2026-59733](https://insights.sbomify.com/CVE-2026-59733/): rclone `serve restic --private-repos` authorization bypass: `..` in the URL path lets an authenticated user read, overwrite and delete other users' repositories (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12907 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2018-12907 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-12907/ (Markdown: https://insights.sbomify.com/CVE-2018-12907/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-12907
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-12907
- OSV: https://osv.dev/vulnerability/CVE-2018-12907

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-12907/
Summaries are generated and may contain mistakes; the official description above is the record.