It was discovered that fsync(2) system call in glusterfs client code leaks memory. An authenticated attacker could use this flaw to launch a denial of service attack by making gluster clients consume memory of the host machine.
Weakness
The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Glusterfs |
Gluster |
3.12.11 (including) |
3.12.14 (excluding) |
| Glusterfs |
Gluster |
4.0.0 (including) |
4.1.4 (excluding) |
| Glusterfs |
Ubuntu |
bionic |
* |
| Glusterfs |
Ubuntu |
esm-apps/bionic |
* |
Potential Mitigations
- 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.
- Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.
- When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.
- Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).
References