dbcve.org
Ras SecurityApplication · Oracle

CVE-2025-30701

HIGH · 7.3 CVSS v3.1 Published 2025-04-15
Fix available
A fix is available. Upgrade to after 23.7 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the RAS Security component of Oracle Database Server. Supported versions that are affected are 19.3-19.26, 21.3-21.17 and 23.4-23.7. Easily exploitable vulnerability allows low privileged attacker having User Account privilege with network access via Oracle Net to compromise RAS Security. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all RAS Security accessible data as well as unauthorized access to critical data or complete access to all RAS Security accessible data. CVSS 3.1 Base Score 7.3 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-276

Files, directories, or resources ship with permissions more open than they need to be, so unintended users can read or modify them. Attackers look for exactly these loose defaults. Remediation means tightening permissions to the minimum required and verifying them at install and at runtime.

General guidance for the incorrect default permissions class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ras SecurityApplication
Affected:>= 19.3, <= 19.26>= 21.3, <= 21.17>= 23.4, <= 23.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 23.7
Vendor patch www.oracle.com →
Recommended fix High confidence

Apply Oracle CPU April 2025 patch - upgrade to 19.27+ (19c), 21.18+ (21c), or 23.8+ (23c)

  1. 1. Review the Oracle Critical Patch Update (CPU) April 2025 for complete patch information: https://www.oracle.com/security-alerts/cpuapr2025.html
  2. 2. Identify the specific patch number for RAS Security component for your Oracle Database version (19c, 21c, or 23c)
  3. 3. Download the applicable patch from Oracle Support using the patch number identified in step 2
  4. 4. Review the patch readme and pre-install requirements documented by Oracle
  5. 5. Apply the patch following Oracle's standard patch application process for Database Server components
  6. 6. After applying the patch, verify the RAS Security component is updated to the fixed version
  7. 7. Test that RAS Security functionality operates normally after the patch application
Caveat Oracle patches typically require downtime and should be tested in a non-production environment first; review patch prerequisites and known issues in the CPU April 2025 documentation

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,250. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30701 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30701 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data