CVE-2023-46738: Authenticated users can crash the CubeFS servers with maliciously crafted requests

Published Jan 3, 2024
·
Updated

A security vulnerability was found in CubeFS HandlerNode 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. There is no evidence of this attack being exploited in the wild. The vulnerability was found during a security audit carried out by Ada Logics in collaboration with OSTIF and the CNCF.

The issue has been patched in v3.3.1. There is no other mitigation besides upgrading.

Other sources

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.

MITRE

Affected Software

2 affected componentsFixes available
go/github.com/cubefs/cubefs<3.3.1
3.3.1
linuxfoundation Cubefs<3.3.1

Event History

Jan 3, 2024
CVE Published
via MITRE·03:35 PM
Data Sourced
via MITRE·03:35 PM
DescriptionSeverityWeakness
Advisory Published
04:13 PM
Data Sourced
via GitHub·04:13 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2023-46738?

CVE-2023-46738 has a medium severity rating, potentially impacting system availability.

2

How do I fix CVE-2023-46738?

To fix CVE-2023-46738, upgrade CubeFS to version 3.3.1 or later.

3

Who is affected by CVE-2023-46738?

Authenticated users of CubeFS prior to version 3.3.1 are affected by CVE-2023-46738.

4

What impacts does CVE-2023-46738 have on CubeFS users?

CVE-2023-46738 can crash the ObjectNode, denying service to other users.

5

Is there a workaround for CVE-2023-46738?

There is no official workaround for CVE-2023-46738; upgrading to the latest version is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203