dbcve.org
Application ServerApplication · Oracle

CVE-2008-0348

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
Multiple unspecified vulnerabilities in the PeopleTools component in Oracle PeopleSoft Enterprise and JD Edwards EnterpriseOne 8.22.18, 8.48.15, and 8.49.07 have unknown impact and remote attack vectors, aka (1) PSE01, (2) PSE03, and (3) PSE04.

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

Multiple critical vulnerabilities (PSE01, PSE03, PSE04) in the PeopleTools component of Oracle PeopleSoft Enterprise and JD Edwards EnterpriseOne versions 8.22.18, 8.48.15, and 8.49.07 allow remote attackers to exploit unknown weaknesses with critical (CVSS 10) severity, though specific technical details of the attack vectors are not disclosed.

MitigationUpgrade affected PeopleTools installations to Oracle-patched versions; apply available CPU patches and implement network segmentation to reduce exposure until upgrades 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
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
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 PeopleTools version via web interface
    Log into PeopleSoft Pure Internet Architecture and navigate to 'About' or 'Version' page, typically found under PeopleTools > Utilities > About
    Affected if The reported PeopleTools version shows 8.47, 8.48, or 8.49
  2. Identify PeopleTools version via SQL query
    Connect to the PeopleSoft database and query PSSTATUS table: SELECT TOOLSREL FROM PSSTATUS
    Affected if The TOOLSREL column returns a value matching 8.47, 8.48, or 8.49
  3. Identify PeopleTools version via command line
    Check the PS_HOME environment variable or inspect the psprcs.cfg configuration file located in PS_HOME\appserv\prcs\<domain>\
    Affected if The Tools Release field shows 8.47, 8.48, or 8.49
  4. Confirm PeopleTools component is exposed
    Verify that PeopleSoft Internet Architecture (PIA) web services are accessible externally or on untrusted networks
    Affected if PeopleTools web interfaces are reachable without proper network segmentation from untrusted zones

If any detection method confirms PeopleTools version 8.47, 8.48, or 8.49 is installed and the web interface is network-accessible, the environment is likely affected by CVE-2008-0348.

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

Upgrade affected PeopleTools installations to Oracle-patched versions; apply available CPU patches and implement network segmentation to reduce exposure until upgrades can be completed.

Recommended fix High confidence

PeopleTools 8.48.16+ or PeopleTools 8.49.08+ (depending on current release line)

  1. 1. Identify the exact PeopleTools version currently installed by checking the PS_HOME directory or PeopleSoft System Properties.
  2. 2. For PeopleTools 8.47: Upgrade to PeopleTools 8.48.16 or higher.
  3. 3. For PeopleTools 8.48: Upgrade to PeopleTools 8.48.16 or higher (which includes the security fixes for PSE01, PSE03, PSE04).
  4. 4. For PeopleTools 8.49: Upgrade to PeopleTools 8.49.08 or higher.
  5. 5. Apply the Oracle Critical Patch Update from January 2008 or later, which addresses CVE-2008-0348.
  6. 6. After upgrade, verify the PeopleTools version matches the fixed release and test critical PeopleSoft components.
  7. 7. Review Oracle PeopleSoft Enterprise and JD Edwards EnterpriseOne documentation for any required post-upgrade steps.
Caveat Major PeopleTools upgrades may require application re-testing, potential customizations review, and database schema updates; coordinate with Oracle support

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

Fix this in Application Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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