Transportation ManagementApplication · Oracle

CVE-2021-2476

MEDIUM · 5.3 CVSS v3.1 Published 2021-10-20
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 Transportation Management product of Oracle Supply Chain (component: Authentication). The supported version that is affected is 6.4.3. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Transportation Management. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Transportation 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 authentication bypass vulnerability in Oracle Transportation Management version 6.4.3. An unauthenticated attacker with network access via HTTP can exploit this flaw to gain unauthorized read access to a subset of the application's data, resulting in a confidentiality breach.

MitigationApply the Oracle security patch for CVE-2021-2476 to upgrade from version 6.4.3, or upgrade to a supported version of Oracle Transportation Management. Restrict network access to the OTM interface as an interim control.

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
Transportation ManagementApplication
Affected:= 6.4.3

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 Transportation Management version
    Locate the installed OTM version through the application admin interface, about page, or version information in the application logs or configuration. Common paths include the OTM home page, /about endpoint, or checking version files in the OTM installation directory.
    Affected if The installed version is exactly 6.4.3 (no other versions are listed as affected)
  2. Verify OTM web interface is HTTP-accessible
    Confirm the Oracle Transportation Management web application is reachable over HTTP or HTTPS from the network. This can be tested by attempting to access the OTM login page or base URL from a remote system.
    Affected if The OTM HTTP/HTTPS interface is exposed to network access
  3. Check for unauthenticated access to sensitive endpoints
    Attempt to access protected OTM data endpoints or API paths without providing credentials. Note: This should only be performed by authorized security personnel on systems they have permission to test.
    Affected if Unauthenticated HTTP requests can retrieve application data without authentication credentials
  4. Confirm OTM component is running
    Verify the Oracle Transportation Management application server is actively running and the OTM web component is operational. Check process lists or service status for OTM-related services.
    Affected if The OTM 6.4.3 application is running and serving HTTP requests

You are affected if Oracle Transportation Management version 6.4.3 is installed and the OTM web interface is accessible over HTTP from the network, allowing unauthenticated attackers to bypass authentication and access data.

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 security patch for CVE-2021-2476 to upgrade from version 6.4.3, or upgrade to a supported version of Oracle Transportation Management. Restrict network access to the OTM interface as an interim control.

Fix this in Transportation 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-2021-2476 — 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-2021-2476 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