dbcve.org
Application ServerApplication · Oracle

CVE-2008-0347

HIGH · 10.0 CVSS v2.0 Published 2008-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Unspecified vulnerability in the Oracle Ultra Search component in Oracle Collaboration Suite 10.1.2; Database 9.2.0.8, 10.1.0.5, and 10.2.0.3; and Application Server 9.0.4.3 and 10.1.2.0.2; has unknown impact and local attack vectors, aka OCS01. NOTE: Oracle has not disputed a reliable claim that this issue is related to WKSYS schema privileges.

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 · moderate confidence

Oracle Ultra Search component vulnerability related to WKSYS schema privilege escalation, allowing local attackers to gain unauthorized access to the Ultra Search schema with elevated privileges.

MitigationApply Oracle Critical Patch Update (CPU) for January 2008 or later, and review/revoke excessive privileges granted to the WKSYS schema per Oracle security guidelines.

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
Application ServerApplication
Affected:= 1.0.2.2= 9.0.4.3= 10.1.2.0.2= 10.1.2.1.0= 10.1.2.2.0= 10.1.3.0.0= 10.1.3.1.0= 10.1.3.3.0
Application Server 9iApplication
Affected:= 9.0.4.3= 10.1.2.0.2
Collaboration SuiteApplication
Affected:= 10.1.2
Database ServerDatabase / datastore
Affected:= 9.0.1.5= 9.2.0.8= 9.2.0.8dv= 10.1.0.5= 10.2.0.2= 10.2.0.3= 11.1.0.6
E Business SuiteApplication
Affected:= 11.5.9= 11.5.10= 11.5.10.2= 12.0.0= 12.0.1= 12.0.2= 12.0.3
Peoplesoft Enterprise PeopletoolsApplication
Affected:= 8.47= 8.48= 8.49

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 product installation
    Query the database or application server for the installed Oracle version. For Database: SELECT VERSION FROM V$INSTANCE; For Application Server: Check OracleAS installation directory and version files.
    Affected if The installed version matches one of the affected versions listed in the CVE (Application Server 1.0.2.2, 9.0.4.3, 10.1.2.x through 10.1.3.3.0; Collaboration Suite 10.1.2; Database 9.0.1.5 through 11.1.0.6; E Business Suite 11.5.9 through 12.0.3; Peoplesoft 8.47-8.49)
  2. Confirm Ultra Search component is installed
    Check for Ultra Search installation. For Database: SELECT * FROM ALL_OBJECTS WHERE OBJECT_NAME LIKE '%ULTRASEARCH%' OR OBJECT_NAME LIKE '%WKSYS%'; For Application Server: Look for Ultra Search instance in the OracleAS management console or check ORACLE_HOME/ultrasearch directory.
    Affected if Ultra Search component is present in the environment
  3. Verify WKSYS schema exists
    Query for WKSYS schema presence: SELECT USERNAME FROM DBA_USERS WHERE USERNAME = 'WKSYS'; or SELECT COUNT(*) FROM ALL_OBJECTS WHERE OWNER = 'WKSYS';
    Affected if The WKSYS schema exists in the database
  4. Check WKSYS schema privileges
    Query for privileges granted to WKSYS: SELECT GRANTEE, PRIVILEGE, TABLE_NAME FROM DBA_TAB_PRIVS WHERE GRANTEE = 'WKSYS'; SELECT GRANTEE, PRIVILEGE FROM DBA_SYS_PRIVS WHERE GRANTEE = 'WKSYS';
    Affected if WKSYS schema has been granted excessive privileges beyond what is required for normal Ultra Search operation, particularly elevated system privileges or access to sensitive schemas
  5. Audit Ultra Search data access
    Examine what data the WKSYS schema can access: SELECT OWNER, TABLE_NAME FROM ALL_TAB_PRIVS WHERE GRANTEE = 'WKSYS' OR GRANTOR = 'WKSYS';
    Affected if WKSYS schema has direct access to sensitive application schemas or data that should be restricted
  6. Review Ultra Search web interface access
    For Application Server deployments, check the Ultra Search URL (typically /ultrasearch) and verify authentication controls. Look for any public or improperly authenticated endpoints.
    Affected if Ultra Search web interface is accessible without proper authentication or authorization controls

A user is affected if they are running any of the listed Oracle product versions with Ultra Search installed and the WKSYS schema exists with elevated or excessive privileges that could allow privilege escalation.

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 Oracle Critical Patch Update (CPU) for January 2008 or later, and review/revoke excessive privileges granted to the WKSYS schema per Oracle security guidelines.

Fix this in Application Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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