# CVE-2023-46742: CubeFS leaks users key in logs

> CubeFS leaks user secret keys in logs, allowing lower-privileged users to impersonate higher-privileged users by accessing log files.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Jan 2024
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-vwch-g97w-hfg2, GO-2024-2434

## What is CVE-2023-46742?

CVE-2023-46742 is a medium-severity vulnerability in cubefs, published on 3 Jan 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

CubeFS is an open-source cloud-native file storage system. CubeFS prior to version 3.3.1 was found to leak users secret keys and access keys in the logs in multiple components. When CubeCS creates new users, it leaks the users secret key. This could allow a lower-privileged user with access to the logs to retrieve sensitive information and impersonate other users with higher privileges than themselves. The issue has been patched in v3.3.1. There is no other mitigation than upgrading CubeFS.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2023-46742?

3 open source packages ship an affected version, including github.com/cubefs/cubefs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/cubefs/cubefs` | Go | All versions | None |
| `github.com/cubefs/cubefs` | Go | All versions | 3.3.1 |
| `github.com/cubefs/cubefs` | Go | All versions | 3.3.1 |

Products: Linuxfoundation Cubefs.

## How do I fix CVE-2023-46742?

Upgrade github.com/cubefs/cubefs to 3.3.1 or later.

## Is CVE-2023-46742 being exploited?

There is no known exploitation of CVE-2023-46742 in the wild and no public exploit code.

## Other vulnerabilities in cubefs

- [CVE-2023-46738](https://insights.sbomify.com/CVE-2023-46738/): Authenticated users can crash the CubeFS servers with maliciously crafted requests (medium 6.5)
- [CVE-2023-46739](https://insights.sbomify.com/CVE-2023-46739/): Timing attack can leak user passwords (medium 6.5)
- [CVE-2023-46740](https://insights.sbomify.com/CVE-2023-46740/): Insecure random string generator used for sensitive data (medium 6.5)
- [CVE-2023-30512](https://insights.sbomify.com/CVE-2023-30512/): CubeFS allows Kubernetes cluster-level privilege escalation (medium 6.5)
- [CVE-2023-46741](https://insights.sbomify.com/CVE-2023-46741/): CubeFS leaks magic secret key when starting Blobstore access service (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46742 and fix it if it is affected.

What it is: CVE-2023-46742 is a medium-severity vulnerability in cubefs, published on 3 Jan 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-46742 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/cubefs/cubefs (Go): affected all versions; no fix listed
- github.com/cubefs/cubefs (Go): affected all versions; fixed in 3.3.1
- github.com/cubefs/cubefs (Go): affected all versions; fixed in 3.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-46742/ (Markdown: https://insights.sbomify.com/CVE-2023-46742/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-46742
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46742
- OSV: https://osv.dev/vulnerability/CVE-2023-46742

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-46742/
Summaries are generated and may contain mistakes; the official description above is the record.