dbcve.org
Fleet Patching And ProvisioningApplication · Oracle

CVE-2025-30702

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-15
Fix available
A fix is available. Upgrade to after 19.26 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Fleet Patching and amp; Provisioning component of Oracle Database Server. Supported versions that are affected are 19.3-19.26. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Fleet Patching and amp; Provisioning. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Fleet Patching and amp; Provisioning accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 · high confidence

CVE-2025-30702 is an information disclosure vulnerability in Oracle Database's Fleet Patching and Provisioning component affecting versions 19.3-19.26. An unauthenticated attacker with network access via HTTP can exploit this flaw to gain unauthorized read access to a subset of Fleet Patching and Provisioning data. The attack requires no authentication and has low complexity.

MitigationApply the Oracle Critical Patch Update (CPU) that addresses CVE-2025-30702 to affected Oracle Database installations. Since this is an unauthenticated HTTP-based vulnerability, restrict network access to Fleet Patching and Provisioning interfaces until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Fleet Patching And ProvisioningApplication
Affected:>= 19.3, <= 19.26

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle Database version
    Query the database version using SQL: SELECT VERSION FROM V$INSTANCE; or check opatch lsinventory output
    Affected if The version falls within 19.3 through 19.26 inclusive
  2. Verify Fleet Patching and Provisioning is installed
    Check for the presence of FPP components via Oracle Inventory or query DBA_REGISTRY for the FPP component status
    Affected if Fleet Patching and Provisioning appears in the installed components list with an ACTIVE status
  3. Confirm FPP HTTP listener is enabled
    Check Oracle listener status (lsnrctl status) and review FPP server configuration for HTTP endpoint availability
    Affected if An HTTP listener is active for Fleet Patching and Provisioning (typically on port 8888 or similar)
  4. Assess network exposure of FPP interface
    Review firewall rules, Oracle Network Configuration, and any exposed HTTP endpoints for the FPP service
    Affected if The FPP HTTP interface is reachable from untrusted networks or external IP addresses

The environment is affected if Oracle Database version is 19.3-19.26 AND Fleet Patching and Provisioning is installed with an accessible HTTP interface exposed to network attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 19.26
Interim mitigation

Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2025-30702 to affected Oracle Database installations. Since this is an unauthenticated HTTP-based vulnerability, restrict network access to Fleet Patching and Provisioning interfaces until the patch can be applied.

Recommended fix Moderate confidence

Oracle Database 19.27 or later (or latest 19c Proactive Bundle/Oracle Database 23c/21c as applicable)

  1. Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2025-30702. Check Oracle Support for the specific patch number for your platform.
  2. Alternatively, upgrade to Oracle Database 19.27 or later (or the latest 19c release) which contains the fix for this vulnerability.
  3. After applying the patch, verify the Fleet Patching and Provisioning component is no longer exposed to unauthorized read access.
  4. Restrict network access to Fleet Patching and Provisioning HTTP interfaces using firewall rules or ACLs if immediate patching is not feasible.
Caveat Oracle patch updates are generally cumulative and low-risk; verify compatibility with your specific environment before applying

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

Fix this in Fleet Patching And Provisioning Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30702 — 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-30702 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