# CVE-2024-12236: Use of Custom URI for media inputs with VPC-SC enabled potentially leads to data exfiltration

> Attackers can exfiltrate data by using custom URIs in Vertex Gemini API requests, bypassing VPC Service Controls security perimeters.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2024
- **Updated:** 30 Jan 2025
- **Also known as:** GHSA-3vm2-3vf9-9j39

## What is CVE-2024-12236?

CVE-2024-12236 is a medium-severity server-side request forgery vulnerability in Google Cloud Platform Vertex Gemini API, published on 10 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security issue exists in Vertex Gemini API for customers using VPC-SC. By utilizing a custom crafted file URI for image input, data exfiltration is possible due to requests being routed outside the VPC-SC security perimeter, circumventing the intended security restrictions of VPC-SC.

No further fix actions are needed. Google Cloud Platform implemented a fix to return an error message when a media file URL is specified in the fileUri parameter and VPC Service Controls is enabled. Other use cases are unaffected.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

## Which versions are affected by CVE-2024-12236?

It affects 1 product.


Products: Google Vertex Gemini Api.

## How do I fix CVE-2024-12236?

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

## Is CVE-2024-12236 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12236 and fix it if it is affected.

What it is: CVE-2024-12236 is a medium-severity server-side request forgery vulnerability in Google Cloud Platform Vertex Gemini API, published on 10 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12236 in the wild and no public exploit code.

Affected product: Google Cloud Platform Vertex Gemini API. 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-2024-12236/ (Markdown: https://insights.sbomify.com/CVE-2024-12236/index.md)
```

## Sources

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

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