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

Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified

What, why and how

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.

What

Why

The product does not handle or incorrectly handles an exceptional condition.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The product does not handle or incorrectly handles an exceptional condition.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → Improper Handling of Exceptional Conditions → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Not a CVSS 4.0 base metric
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-755 ↗
CWE-755: Improper Handling of Exceptional Conditions. The product does not handle or incorrectly handles an exceptional condition.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: 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
Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCHighSubsequent-system confidentiality: A successful attack can cause a major loss.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

CWE-755

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2024-50703Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

Cyber Security Agency of Singapore · English · CSA-SB-20241211Security Bulletin 11 Dec 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 11 Dec 2024, published on 11 December 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2024-026456Google の Vertex AI Gemini API における例外的な状態の処理に関する脆弱性

Google の Vertex AI Gemini API には、例外的な状態の処理に関する脆弱性が存在します。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Fix not verified
Affected: Vertex Gemini API: version range in vendor record
Fixed: No fixed version is explicitly recorded in the structured CVE data.
Action: No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 10 Dec 2024 · Last source change 30 Jan 2025, 09:03 UTC · CWE-755 · Improper Handling of Exceptional Conditions

CVE recordCVE.org · 5.1

CVSS sourceCNA

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2024-50703

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceCNA

NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2024-12-10CVE published

ENISA EUVD · EUVD-2024-50703↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Use of Custom URI for media inputs with VPC-SC enabled potentially leads to data exfiltration

Published severity in operational context

Evidence used

Compensating controls

Verification

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2024-50703