CubeFS leaks magic secret key when starting Blobstore access serviceGHSA-8h2x-gr2c-c275
MEDIUMFix: cubefs/cubefs@972f027GHSA-8h2x-gr2c-c275 is a medium-severity (CVSS 4.8) Information Exposure vulnerability in github.com/cubefs/cubefs. A fix is available for github.com/cubefs/cubefs — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-8h2x-gr2c-c275.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/cubefs/cubefsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
A vulnerability was found in CubeFS that could allow users to read sensitive data from the logs which could allow them escalate privileges.
CubeFS leaks configuration keys in plaintext format in the logs. These keys could allow anyone to carry out operations on blobs that they otherwise do not have permissions for. For example, an attacker that has succesfully retrieved a secret key from the logs can delete blogs from the blob store.
The attacker can either be an internal user with limited privileges to read the log, or it can be an external user who has escalated privileges sufficiently to access the logs. There is no evidence of this vulnerability being exploited in the wild. It was found during an ongoing security audit carried out by Ada Logics in collaboration with OSTIF and the CNCF.
The vulnerability has been patched in v3.3.1. There is no other mitigated than upgrading.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/cubefs/cubefs | all versions | 3.3.1go get github.com/cubefs/cubefs@v3.3.1 |
Affected Products
cubefslinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cubefs/cubefs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cubefs/cubefs to 3.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8h2x-gr2c-c275 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-8h2x-gr2c-c275 in your dependencies?
Find it across Go, including transitive dependencies.