dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2025-53047

MEDIUM · 5.8 CVSS v3.1 Published 2025-10-21
Fix available
A fix is available. Upgrade to after 23.9 or later.
See remediation →
67/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 Portable Clusterware component of Oracle Database Server. Supported versions that are affected are 19.3-19.28, 21.3-21.19 and 23.4-23.9. Easily exploitable vulnerability allows unauthenticated attacker with network access via Bonjour to compromise Portable Clusterware. While the vulnerability is in Portable Clusterware, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized read access to a subset of Portable Clusterware accessible data. CVSS 3.1 Base Score 5.8 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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

Unauthenticated remote attacker can exploit Oracle Portable Clusterware via the Bonjour protocol to gain unauthorized read access to a subset of accessible data. The vulnerability affects Oracle Database Server versions 19.3-19.28, 21.3-21.19, and 23.4-23.9, with scope extension potentially impacting additional products in the environment.

MitigationApply Oracle Critical Patch Updates for the affected versions. As an interim control, restrict or disable Bonjour (mDNS) network access to Portable Clusterware components.

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
Database ServerDatabase / datastore
Affected:>= 19.3, <= 19.28>= 21.3, <= 21.19>= 23.4, <= 23.9

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
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 Server version
    Run 'sqlplus / as sysdba' and execute 'SELECT VERSION FROM V$INSTANCE;' or use 'lsnrctl status' to check the Oracle version installed
    Affected if The installed version falls within 19.3-19.28, 21.3-21.19, or 23.4-23.9
  2. Determine if Portable Clusterware is configured
    Check for Oracle Clusterware resources using 'crsctl status resource -t' or 'srvctl status cluster' if Oracle Clusterware is installed
    Affected if Portable Clusterware is running or configured on the system
  3. Check if mDNS/Bonjour service is enabled
    Verify if mDNS responder is running: on Linux check 'systemctl status avahi-daemon' or 'ps -ef | grep mDNS'; on Windows check service 'Bonjour Service'. Also check if port 5353 is listening using 'netstat -an | grep 5353'
    Affected if The mDNS (Bonjour) service is running and port 5353 is open
  4. Assess network exposure of mDNS service
    Use 'netstat -an' or 'nmap -sU -p 5353 <target>' to verify if port 5353 is bound to a non-loopback interface and accessible from network segments
    Affected if Port 5353 is listening on a routable network interface (not 127.0.0.1)

If the Oracle Database Server version is within the affected ranges (19.3-19.28, 21.3-21.19, 23.4-23.9), Portable Clusterware is configured, and mDNS/Bonjour (port 5353) is enabled and exposed on the network, the environment is vulnerable to unauthorized read access.

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.

From vendor data
Upgrade available Upgrade to a release after 23.9
Interim mitigation

Apply Oracle Critical Patch Updates for the affected versions. As an interim control, restrict or disable Bonjour (mDNS) network access to Portable Clusterware components.

Fix this in Database Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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