Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-22072 is a critical-severity Missing Authentication for Critical Function (CWE-306) vulnerability in Oracle Weblogic Server. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique VNC (T1021.005); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-26237
Vulnerability Data
Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Core). The supported version that is affected is 12.2.1.3.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3, IIOP to compromise Oracle WebLogic Server. Successful attacks…
more
of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 3 OS baselines
V6.2.3V6.4.4V10.4.16V12.1.3
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requires established identification and authentication to unlock, mitigating missing authentication for continued system access.
Requiring identification and rationale for actions allowed without authentication ensures critical functions are not left unprotected by forcing review of authentication requirements.
Authorizing mobile device connections to organizational systems ensures authentication is performed for this critical access function.
Guarantees critical functions are protected by mandatory invocation of the access control mechanism.
Auditing sessions makes it possible to detect access to critical functions without required authentication.
The assessment process confirms authentication is present and effective for critical functions, preventing exploitation from missing authentication.
Certification assesses that critical functions have required authentication controls in place.
Disabling non-essential functions and services eliminates the need to secure them, reducing exposure from missing authentication on unnecessary components.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Directly requires authentication of users/services/hardware, which eliminates missing authentication for critical functions.
Managing identities and credentials is a prerequisite for authentication but does not itself enforce it on critical functions.
Defining and enforcing authorizations assumes prior authentication and therefore only partially mitigates the absence of authentication.
Protecting networks from unauthorized access can be undermined by missing authentication but does not address the root authentication gap.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.5 mandates that authentication be in place to substantiate claimed identity when access to systems, applications and services is granted, and CWE-306 is the absence of authentication for critical functions; applying A.8.5 where it was not applied before requires adding authentication, so the weakness stops being present with no remainder, analogous to A.8.24 -> CWE-311 = full.
A.8.29 explicitly tests authentication functions and combines code review, dynamic testing, and penetration testing that surface most missing-authentication flaws, while a bounded remainder remains in secondary channels, undisclosed binary components, and operational/post-deployment exposures that one test cycle may not enumerate.
A.8.3 mandates authentication for access to information and associated assets (explicit in the dynamic access management section: 'requiring authentication, appropriate credentials or a certificate'), so implementing it where it was not applied before adds authentication to critical functions that lacked it, removing most CWE-306 instances; the remainder is nameable — secondary channels that bypass the primary authentication path, debug/UART ports, and protocol-level gaps in OT/embedded systems where access restriction is enforced at a different layer than the clause reaches.
Training developers to recognize authentication requirements can reduce some instances of this architectural omission, but CWE-306 is primarily a design-time oversight rather than a knowledge gap or deliberate choice, so education moves only a minority of cases.
Network controls (firewalls, network authentication, filtering, segmentation) can block external or unauthorized network access to an unauthenticated critical function, but the missing authentication remains in the application and is still exploitable by anyone who reaches the service path — including internal users, anyone bypassing the firewall, or cases where the function is intentionally network-exposed.
A.8.21 mandates authentication requirements for accessing network services and requires security measures (including authentication) to be identified and implemented, so applying it where it was not applied before results in authentication being added to network services that lacked it, removing those CWE-306 instances; however, A.8.21's scope is limited to network services while CWE-306 also covers non-network critical functions (UART debug ports, local APIs, backdoor channels), and the clause governs the requirement rather than directly implementing authentication, leaving a nameable remainder.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
Oracle Linux 8 (2 partial rules)
- V-248585 OL 8 must require reauthentication when using the "sudo" command. blocks CWE-306
- V-248827 OL 8 must not have the rsh-server package installed. blocks CWE-306
RHEL 7 (1 rule, 1 more partial)
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. blocks CWE-306
- V-237635 The Red Hat Enterprise Linux operating system must require re-authentication when using the "sudo" command. blocks CWE-306
RHEL 8 (1 rule, 1 more partial)
- V-230492 RHEL 8 must not have the rsh-server package installed. blocks CWE-306
- V-237643 RHEL 8 must require re-authentication when using the "sudo" command. blocks CWE-306