Communications Order And Service ManagementApplication · Oracle

CVE-2025-21554

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Oracle Communications Order and Service Management product of Oracle Communications Applications (component: Security). Supported versions that are affected are 7.4.0, 7.4.1 and 7.5.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Communications Order and Service Management. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Communications Order and Service Management 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

This is an information disclosure vulnerability in Oracle Communications Order and Service Management (versions 7.4.0, 7.4.1, 7.5.0) that allows unauthenticated remote attackers via HTTP to read a subset of accessible data. The attack requires network access but needs no authentication or user interaction, leveraging low complexity.

MitigationApply the Oracle patch for this vulnerability once released. Until then, restrict network access to the affected system and monitor for unauthorized access attempts.

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
Communications Order And Service ManagementApplication
Affected:= 7.4.0= 7.4.1= 7.5.0

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. Confirm Oracle Communications Order and Service Management is installed
    Locate the product installation directory or running process. Common paths include $ORACLE_HOME/osm or check for processes named 'osm' or 'OrderAndServiceManagement'. Use 'ps -ef | grep -i osm' on Linux or check Windows services.
    Affected if The product is present on the system
  2. Identify the installed version
    Check the version of Oracle Communications Order and Service Management. Look for a version file in the installation directory, check the admin console login page for version display, or query the application's /version endpoint if available. Compare against 7.4.0, 7.4.1, and 7.5.0.
    Affected if The installed version is exactly 7.4.0, 7.4.1, or 7.5.0
  3. Verify HTTP interface is network-accessible
    Determine if the OSM HTTP ports (default 8080 or 8000, or configured HTTPS ports) are exposed to the network. Use 'netstat -tlnp | grep -E "(8080|8000)"' or review firewall rules and load balancer configurations.
    Affected if The HTTP interface is reachable from untrusted network segments
  4. Check for unauthorized access attempts in HTTP logs
    Review OSM HTTP access logs for unexpected or anomalous requests, particularly to data endpoints. Look for unusual query patterns, unexpected IP sources, or requests outside normal business hours.
    Affected if Logs show unauthorized or suspicious HTTP requests to data retrieval endpoints

A system is affected if Oracle Communications Order and Service Management versions 7.4.0, 7.4.1, or 7.5.0 are installed and their HTTP interface is network-accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle patch for this vulnerability once released. Until then, restrict network access to the affected system and monitor for unauthorized access attempts.

Fix this in Communications Order And Service Management 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 help mitigating

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-21554 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-21554 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