dbcve.org
TuxedoApplication · Oracle

CVE-2017-10269

CRITICAL · 10.0 CVSS v3.0 Published 2017-11-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 Tuxedo component of Oracle Fusion Middleware (subcomponent: Core). Supported versions that are affected are 11.1.1, 12.1.1, 12.1.3 and 12.2.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via Jolt to compromise Oracle Tuxedo. While the vulnerability is in Oracle Tuxedo, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Tuxedo accessible data as well as unauthorized access to critical data or complete access to all Oracle Tuxedo accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Tuxedo. CVSS 3.0 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L).

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

Oracle Tuxedo Jolt protocol handler contains an easily exploitable flaw allowing unauthenticated remote attackers to create, modify, or delete critical data, or gain full unauthorized access to all Tuxedo accessible data. The attack vector is network-based via the Jolt service, with complete confidentiality and integrity impact and partial availability impact.

MitigationApply the Oracle Tuxedo security patches for version 11.1.1, 12.1.1, 12.1.3, or 12.2.2 as appropriate. If immediate patching is not feasible, restrict network access to the Jolt listener port and disable Jolt if not required.

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
TuxedoApplication
Affected:= 11.1.1= 12.1.1= 12.1.3= 12.2.2

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
High
Integrity
High
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L

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 Tuxedo installation
    Locate Tuxedo installation directories (commonly under /tuxedo, /opt/tuxedo, or C:\tuxedo) and look for Tuxedo executables or configuration files such as tuxconfig, TUXCONFIG environment variable, or the presence of Tuxedo binaries (tmadmin, tmboot, tmshutdown).
    Affected if Tuxedo software is found on the system.
  2. Verify Tuxedo version
    Run the Tuxedo version command if available (such as 'tmadmin -v' or check for a version file in the installation directory), or examine Tuxedo release files within the installation path.
    Affected if The installed version matches exactly 11.1.1, 12.1.1, 12.1.3, or 12.2.2.
  3. Determine if Jolt service is enabled
    Check Tuxedo configuration files (UBBCONFIG or tuxconfig) for JOLT entries, or look for Jolt-related processes or listeners. Inspect the Tuxedo configuration for 'JSL' (Jolt Server Listener) or 'JREPOS' entries that activate the Jolt protocol handler.
    Affected if Jolt (JSL/JREPOS) is configured and enabled in the Tuxedo configuration.
  4. Confirm Jolt listener is active
    Query running processes for Jolt-related services, or check network listening ports associated with the Jolt service. Use commands like 'netstat' or 'ss' to identify ports configured for Jolt communication.
    Affected if The Jolt service is listening on a network port and actively running.
  5. Assess network exposure of Jolt port
    Identify the port(s) the Jolt service is bound to from the Tuxedo configuration, then verify whether these ports are exposed to untrusted networks or accessible from external IP addresses.
    Affected if The Jolt listener port is reachable from network segments that include untrusted or external hosts.

The environment is affected if Oracle Tuxedo version 11.1.1, 12.1.1, 12.1.3, or 12.2.2 is installed WITH the Jolt protocol handler enabled and the Jolt service listening on an accessible network port.

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
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Apply the Oracle Tuxedo security patches for version 11.1.1, 12.1.1, 12.1.3, or 12.2.2 as appropriate. If immediate patching is not feasible, restrict network access to the Jolt listener port and disable Jolt if not required.

Recommended fix High confidence

Upgrade to Tuxedo 12.2.2 or later, or apply the October 2017 Critical Patch Update for your specific version

  1. 1. Review the Oracle Critical Patch Update advisory for October 2017 at the vendor URL to obtain the specific patch for your Tuxedo version.
  2. 2. Identify your exact Tuxedo version by running the tmadmin version command or checking the installation.
  3. 3. Download the appropriate patch from Oracle Support for your specific version (11.1.1, 12.1.1, 12.1.3, or 12.2.2).
  4. 4. Apply the Oracle patch following the instructions in the patch readme file.
  5. 5. Alternatively, upgrade to a later supported Tuxedo version that includes the fix (version 12.2.2 or later).
  6. 6. After applying the patch or upgrade, restart all Tuxedo services and verify the Jolt listener is functioning correctly.
  7. 7. Test that the vulnerability is no longer exploitable by attempting the attack vector described in the advisory.
Caveat Review Oracle upgrade documentation for breaking changes between major versions; test in non-production environment first

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

Fix this in Tuxedo 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 patch applied

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-2017-10269 — 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-2017-10269 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