CYBERSECURITYTRACKER
TRACKING7,472 stories in this site build1,582 vulnerability news stories in this site build
Vulnerabilities

CVE-2024-6587

Review this vulnerability's source-backed evidence, with unavailable values and read failures kept distinct.

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker data as of: .

Detection and validation

Mapped metadata availability only. These signals do not change priority.

  • Sigma

    Not mapped by tracked sources.

  • Atomic

    Not mapped by tracked sources.

  • Nuclei

    LiteLLM - Server-Side Request Forgery. Check identifier: CVE-2024-6587.

    Open Nuclei metadata

  • Metasploit

    Not mapped by tracked sources.

What it is

Reported

A Server-Side Request Forgery (SSRF) vulnerability exists in berriai/litellm version 1.38.10. This vulnerability allows users to specify the `api_base` parameter when making requests to `POST /chat/completions`, causing the application to send the request to the domain specified by `api_base`. This request includes the OpenAI API key. A malicious user can set the `api_base` to their own domain and intercept the OpenAI API key, leading to unauthorized access and potential misuse of the API key.

Source reported · Source: NVD · Source last published: · Source description excerpt; complete tracked detail loads below. · Source last updated: · Tracker data as of:

What is affected

Reported

LiteLLM; LiteLLM. Product-level identification only; no affected-version conclusion is available from this field.

Source reported · Source: NVD · Source last published: · Source last updated: · Tracker data as of:

Urgency and basis

Reported

Act · 450.3

Tracker computed · Tracker decision tier from the evidence detailed below · Source last updated: · Tracker data as of:

Exploitation evidence

Reported

listed by a tracked exploitation catalog · VulnCheck KEV

Source reported · VulnCheck KEV added: · Source last updated: · Tracker data as of:

What to do

Reported

Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Source remediation ↗

Source reported · Tracked source remediation field · Source last updated: · Tracker data as of:

Evidence detail

Loading the full tracker evidence record…

Glossary

Open in glossary