ollama: Improper Resource Shutdown or Release
CVE-2024-39721 is a high-severity improper resource shutdown or release vulnerability in ollama, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 0.1.34 as the first without the flaw, so updating ollama to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 2.67% chance of exploitation within 30 days, higher than 86% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update ollama to 0.1.34 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CISA (ADP).
Official description
An issue was discovered in Ollama before 0.1.34. The CreateModelHandler function uses os.Open to read a file until completion. The req.Path parameter is user-controlled and can be set to /dev/random, which is blocking, causing the goroutine to run infinitely (even after the HTTP request is aborted by the client).
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Resource Shutdown or Release
The product does not release or incorrectly releases a resource before it is made available for re-use.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
- It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free memory in a function. If you allocate memory that you intend to free upon completion of the function, you must be sure to free the memory at all exit points for that function including error conditions.
- Memory should be allocated/freed using matching functions such as malloc/free, new/delete, and new[]/delete[].
More Improper Resource Shutdown or Release vulnerabilities (CWE-404)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- oligo.security/blog/more-models-more-probllmsExploit, Third Party Advisory
Other references
Other vulnerabilities in ollama
- 7.3 High severity
- 9.4 Critical severity
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Recent Improper Resource Shutdown or Release vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.1 High severity
Spotted an error? Tell us.