CVE-2024-28224
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOllama before 0.1.29 has a DNS rebinding vulnerability that can inadvertently allow remote access to the full API, thereby letting an unauthorized user chat with a large language model, delete a model, or cause a denial of service (resource exhaustion).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOllama before version 0.1.29 is vulnerable to DNS rebinding attacks, which can bypass the localhost binding protection and allow unauthorized remote access to the full API. An attacker can exploit this to interact with LLMs, delete models, or exhaust server resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.1.29CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Ollama versionRun 'ollama --version' or check the binary version with 'ollama version'Affected if Version is below 0.1.29 (e.g., 0.1.28, 0.1.20, etc.)
-
Verify Ollama process is runningRun 'ps aux | grep ollama' or check if the ollama service is activeAffected if Ollama is running and exposed to network
-
Identify network binding configurationRun 'ss -tlnp | grep 11434' or 'netstat -tlnp | grep 11434' to see which address the Ollama API port (default 11434) is listening onAffected if Port 11434 is bound to 0.0.0.0 or an external IP rather than 127.0.0.1 only
-
Test remote API accessibilityFrom another machine, run 'curl http://<target-ip>:11434/' to see if the API respondsAffected if The API responds to requests from a non-localhost IP address
You are affected if Ollama version is below 0.1.29 AND the API port (11434) is accessible from remote hosts rather than bound to localhost only.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.1.29
Upgrade Ollama to version 0.1.29 or later, which includes DNS rebinding protection. Additionally, consider network segmentation and firewall rules to limit API exposure.
Ollama version 0.1.29 or later
- Check the current installed version of Ollama by running 'ollama --version'
- Stop the Ollama service if it is currently running
- Upgrade Ollama to version 0.1.29 or a later version. For example, on systems with automatic updates, ensure the package manager pulls the latest version. For manual installations, download and install the updated binary from the official Ollama releases
- Restart the Ollama service after the upgrade
- Verify the installed version is 0.1.29 or later using 'ollama --version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28224 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28224 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data