How severe is CVE-2022-39397?

CVE-2022-39397 has a CVSS score of 5.6/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-39397?

CVE-2022-39397 affects the following packages: aliyun-oss-client (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2022-39397?

Update aliyun-oss-client to 0.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-39397 is resolved across your whole dependency graph.

How do I detect CVE-2022-39397 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aliyun-oss-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-39397 if there is no patch (or I can't update yet)?

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.

Is CVE-2022-39397 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-39397 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-39397?

CVE-2022-39397 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-39397?

CVE-2022-39397 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-39397 published, and has it been updated?

CVE-2022-39397 was published on November 22, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

MEDIUM severity

CVE-2022-39397 — aliyun-oss-client

MEDIUMFix: tu6ge/oss-rs@e4553f7

CVE-2022-39397 is a medium-severity (CVSS 5.6) Information Exposure vulnerability in aliyun-oss-client. A fix is available for aliyun-oss-client — see the affected versions and patch details below.

Exposure of sensitive information in aliyun-oss-client

Also known asGHSA-3w3h-7xgx-grwcRUSTSEC-2022-0089

Published

Nov 22, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 CVE-2022-39397.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

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

1 pkg affected

🦀aliyun-oss-client

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Users of this library will be affected when using this library, the incoming secret will be disclosed unintentionally.

Patches

This have already been solved.

Workarounds

No, It cannot be patched without upgrading

References

For more information

If you have any questions or comments about this advisory:

Email us at email address

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`aliyun-oss-client`	all versions	0.8.1`cargo update -p aliyun-oss-client --precise 0.8.1`

Affected Products

1 product · 1 configurations

Application

aliyun-oss-clientaliyun-oss-client_project

< 0.8.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aliyun-oss-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aliyun-oss-client to 0.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-39397 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

### Impact Users of this library will be affected when using this library, the incoming secret will be disclosed unintentionally. ### Patches This have already been solved. ### Workarounds No, It cannot be patched without upgrading ### References No ### For more information If you have any questions or comments about this advisory: * Email us at [email address](mailto:[email protected])