Insecure random string generator used for sensitive data

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.2 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:L · score source

EPSS

• CVE-2023-46740: 0.44% estimated exploitation activity in the next 30 days; percentile 38.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

CubeFS used an insecure random string generator to generate user-specific, sensitive keys used to authenticate users in a CubeFS deployment. This could allow an attacker to predict and/or guess the generated string and impersonate a user thereby obtaining higher privileges. When CubeFS creates new users, it creates a piece of sensitive information for the user called the “accessKey”. To create the "accesKey", CubeFS uses an insecure string generator which makes it easy to guess and thereby impersonate the created user. An attacker could leverage the predictable random string generator and guess a users access key and impersonate the user to obtain higher privileges. There is no evidence of this vulnerability being exploited in the wild. It was found during a security audit carried out by Ada Logics in collaboration with OSTIF and the CNCF. The issue has been fixed in v3.3.1. There is no other mitigation than to upgrade.

Published by the source

3 Jan 2024, 16:14 UTC

Last modified by the source

18 Nov 2024, 16:26 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4248-p65p-hcrm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-46740

Advisory: Insecure random string generator used for sensitive data
IDs: CVE-2023-46740, GHSA-4248-p65p-hcrm
Record: https://patchnext.com/advisories/cve-2023-46740 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/cubefs/cubefs 3.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cubefs/cubefs: affected < 3.3.1; fixed in 3.3.1

## Suggested inspection (read-only)
- Go github.com/cubefs/cubefs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cubefs/cubefs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4248-p65p-hcrm (GitHub-reviewed advisory GHSA-4248-p65p-hcrm lists affected ranges: Go github.com/cubefs/cubefs >=0 <3.3.1)

Commands are suggestions: review each one before running it.