# CVE-2021-2351: Weak cryptography in WebLogic Server

> An unauthenticated attacker can compromise the Advanced Networking Option via weak ciphers, leading to full takeover of the component.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Jul 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gm3p-p24r-4wxq

## What is CVE-2021-2351?

CVE-2021-2351 is a high-severity vulnerability in Oracle Agile Product Lifecycle Management, published on 20 Jul 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Advanced Networking Option component of Oracle Database Server. Supported versions that are affected are 12.1.0.2, 12.2.0.1 and 19c. Difficult to exploit vulnerability allows unauthenticated attacker with network access via Oracle Net to compromise Advanced Networking Option. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Advanced Networking Option, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Advanced Networking Option. Note: The July 2021 Critical Patch Update introduces a number of Native Network Encryption changes to deal with vulnerability CVE-2021-2351 and prevent the use of weaker ciphers. Customers should review: "Changes in Native Network Encryption with the July 2021 Critical Patch Update" (Doc ID 2791571.1). CVSS 3.1 Base Score 8.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H).

Weakness: CWE-384 (Session Fixation), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2021-2351?

It affects 111 products.


Products: Oracle Advanced Networking Option, Oracle Agile Engineering Data Management, Oracle Agile Product Lifecycle Management, Oracle Agile Product Lifecycle Management for Process, Oracle Airlines Data Model, Oracle Application Performance Management, Oracle Application Testing Suite, Oracle Argus Analytics, Oracle Argus Insight, Oracle Argus Mart, Oracle Argus Safety, Oracle Banking Apis, Oracle Banking Digital Experience, Oracle Banking Enterprise Default Management, Oracle Banking Platform, Oracle Big Data Spatial and Graph, Oracle Blockchain Platform, Oracle Clinical, Oracle Commerce Platform, Oracle Communications Application Session Controller and 91 more.

## How do I fix CVE-2021-2351?

No fix has been published for CVE-2021-2351 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-2351 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-2351 and fix it if it is affected.

What it is: CVE-2021-2351 is a high-severity vulnerability in Oracle Agile Product Lifecycle Management, published on 20 Jul 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-2351 in the wild and no public exploit code.

Affected product: Oracle Agile Product Lifecycle Management. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2021-2351/ (Markdown: https://insights.sbomify.com/CVE-2021-2351/index.md)
```

## Sources

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

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