dbcve.org
TeleserviceApplication · Oracle

CVE-2025-30717

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-15
Fix available
A fix is available. Upgrade to after 12.2.14 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Oracle Teleservice product of Oracle E-Business Suite (component: Service Diagnostics Scripts). Supported versions that are affected are 12.2.3-12.2.14. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Teleservice. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Teleservice accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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

Information disclosure vulnerability in Oracle Teleservice Service Diagnostics Scripts allows low-privileged attackers with network access via HTTP to access critical data due to improper access controls in the diagnostics functionality.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for Oracle E-Business Suite that addresses CVE-2025-30717. Prior to production deployment, test the patch in a non-production environment to verify no functional regressions.

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
TeleserviceApplication
Affected:>= 12.2.3, <= 12.2.14

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Confirm Oracle Teleservice component is installed
    Query the Oracle E-Business Suite application for the presence of the Teleservice module. This can typically be done by checking the Oracle EBS product table (e.g., fnd_product_installations) or by reviewing the application banner/accessing the Teleservice responsibility if available.
    Affected if Oracle Teleservice is not installed, the system is not affected by this specific vulnerability.
  2. Identify the installed Oracle Teleservice version
    Retrieve the version number of the Oracle Teleservice component. In Oracle EBS, this is typically available through the application banner, the patch level information in the Oracle Applications Manager (OAM), or by querying the FND_PRODUCT_GROUPS or similar EBS version tables.
    Affected if The installed version falls within the range >= 12.2.3 and <= 12.2.14, meaning the version is affected.
  3. Verify the Service Diagnostics Scripts are accessible
    Determine whether the diagnostic scripts functionality within Oracle Teleservice is exposed and accessible. This typically involves checking if the diagnostic endpoints or scripts are reachable via HTTP/HTTPS network access without elevated privileges.
    Affected if The diagnostic scripts are accessible over the network to low-privileged users, indicating potential exploitation exposure.
  4. Check network accessibility of the Teleservice interface
    Assess whether the Oracle Teleservice application is accessible over HTTP/HTTPS from the network. This includes verifying if the OAF or JSP pages used by Teleservice diagnostics are exposed externally or to untrusted networks.
    Affected if The Teleservice interface (including diagnostics) is reachable via network access using the HTTP protocol.

A system is affected if it runs Oracle Teleservice version 12.2.3 through 12.2.14, has the diagnostic functionality exposed, and is accessible over the network to low-privileged 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 12.2.14
Interim mitigation

Apply the relevant Oracle Critical Patch Update (CPU) for Oracle E-Business Suite that addresses CVE-2025-30717. Prior to production deployment, test the patch in a non-production environment to verify no functional regressions.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.15 or later

  1. 1. Review Oracle E-Business Suite 12.2.15 release notes and patch announcements for security fixes related to CVE-2025-30717
  2. 2. Ensure you have a complete backup of the current Oracle E-Business Suite environment
  3. 3. Test the upgrade in a non-production environment before deploying to production
  4. 4. Apply Oracle's recommended patches for the Teleservice component (Service Diagnostics Scripts)
  5. 5. Verify the vulnerability is remediated by checking that the affected scripts are no longer exposed or have been patched
  6. 6. Confirm normal Teleservice functionality after patching
Caveat Review Oracle 12.2.15 release notes for any functional changes to Teleservice module; some custom integrations may require testing

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

Fix this in Teleservice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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