dbcve.org
DatabaseDatabase / datastore · Oracle

CVE-2017-3567

MEDIUM · 5.3 CVSS v3.0 Published 2017-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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 OJVM component of Oracle Database Server. Supported versions that are affected are 11.2.0.4 and 12.1.0.2. Difficult to exploit vulnerability allows low privileged attacker having Create Session, Create Procedure privilege with network access via multiple protocols to compromise OJVM. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of OJVM. CVSS 3.0 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H).

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 a denial-of-service vulnerability in the Oracle Java Virtual Machine (OJVM) component of Oracle Database Server. A low-privileged attacker with Create Session and Create Procedure database privileges can exploit this flaw via network access to cause OJVM to hang or crash repeatedly. The attack complexity is rated as high, requiring specific privileges but no user interaction.

MitigationApply the Oracle Critical Patch Update (CPU) for April 2017 or later that addresses CVE-2017-3567. Alternatively, restrict network access to the database and limit the Create Session and Create Procedure privileges to only essential users until patching can be completed.

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
DatabaseDatabase / datastore
Affected:= 11.2.0.4= 12.1.0.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 version
    Run the query: SELECT VERSION FROM V$INSTANCE; or check the Oracle inventory for the installed database version.
    Affected if The version is 11.2.0.4 or 12.1.0.2, as these are the affected versions listed.
  2. Verify OJVM component is installed
    Query DBA_REGISTRY or V$OPTION to check if Java Virtual Machine is installed: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Java%';
    Affected if OJVM is present in the database, as the vulnerability exists in the Java Virtual Machine component.
  3. Check if network access is enabled
    Review Oracle Net configuration files (listener.ora, sqlnet.ora) and check if the database is configured for network listener connections.
    Affected if The database accepts network connections, as the attacker requires network access to exploit this flaw.
  4. Audit Create Session privilege assignments
    Query: SELECT GRANTEE, PRIVILEGE FROM DBA_TAB_PRIVS WHERE GRANTEE <> 'PUBLIC' AND PRIVILEGE = 'CREATE SESSION'; or check DBA_ROLE_PRIVS for roles with Create Session.
    Affected if Multiple non-essential users or roles have Create Session privilege, providing potential attack vectors.
  5. Audit Create Procedure privilege assignments
    Query: SELECT GRANTEE, PRIVILEGE FROM DBA_TAB_PRIVS WHERE PRIVILEGE = 'CREATE PROCEDURE'; or check role grants for this privilege.
    Affected if Users or roles other than essential Java developers or administrators have Create Procedure privilege, which is required for exploitation.

A user is affected if they run Oracle Database 11.2.0.4 or 12.1.0.2 with OJVM installed and accessible over the network, where low-privileged users hold both Create Session and Create Procedure privileges.

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 Critical Patch Update (CPU) for April 2017 or later that addresses CVE-2017-3567. Alternatively, restrict network access to the database and limit the Create Session and Create Procedure privileges to only essential users until patching can be completed.

Fix this in Database Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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