Cubefs vulnerabilitiesRanked by how likely they are to be used.
Cubefs is made by Linuxfoundation. We track 6 published vulnerabilities in it, across 26 versions. None of them is on the list of flaws known to be exploited today. If you run Cubefs, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Cubefs vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Cubefs's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Cubefs flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.6%CVE-2023-46738Medium
CubeFS is an open-source cloud-native file storage system.
- 0.5%CVE-2023-30512Medium
CubeFS through 3.2.1 allows Kubernetes cluster-level privilege escalation.
- 0.4%CVE-2023-46740Medium
CubeFS is an open-source cloud-native file storage system.
- 0.4%CVE-2023-46739Medium
CubeFS is an open-source cloud-native file storage system.
- 0.3%CVE-2023-46741Medium
CubeFS is an open-source cloud-native file storage system.
- 0.3%CVE-2023-46742Medium
CubeFS is an open-source cloud-native file storage system.
Running Cubefs? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
CubeFS is an open-source cloud-native file storage system. A security vulnerability was found in CubeFS HandlerNode in versions prior to 3.3.1 that could allow authenticated users to send maliciously-crafted requests that would crash the ObjectNode and deny other users from using it. The root cause was improper handling of incoming HTTP requests that could allow an attacker to control the ammount of memory that the ObjectNode would allocate. A malicious request could make the ObjectNode allocate more memory that the machine had available, and the attacker could exhaust memory by way of a single malicious request. An attacker would need to be authenticated in order to invoke the vulnerable code with their malicious request and have permissions to delete objects. In addition, the attacker would need to know the names of existing buckets of the CubeFS deployment - otherwise the request would be rejected before it reached the vulnerable code. As such, the most likely attacker is an inside user or an attacker that has breached the account of an existing user in the cluster. The issue has been patched in v3.3.1. There is no other mitigation besides upgrading.
- Matched to
- Cubefs on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 6 published vulnerabilities listed under the name Cubefs, across 26 versions.
None of Cubefs's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Cubefs. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.