CVE-2008-2622
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 · uneditedUnspecified vulnerability in the PeopleSoft PeopleTools component in Oracle PeopleSoft Enterprise and JD Edwards EnterpriseOne 8.48.17 and 8.49.11 has unknown impact and remote authenticated attack vectors, a different vulnerability than CVE-2008-2615, CVE-2008-2616, CVE-2008-2617, CVE-2008-2618, CVE-2008-2620, and CVE-2008-2621.
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 confidenceAuthenticated remote vulnerability in Oracle PeopleSoft Enterprise and JD Edwards EnterpriseOne PeopleTools affecting versions 8.48.17 and 8.49.11. The specific nature of the flaw is unspecified in the CVE, but it is reachable remotely by authenticated attackers.
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= 8.48.17= 8.49.11= 8.48.17= 8.49.11all versionsCVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify PeopleSoft or JD Edwards installationCheck for Oracle PeopleSoft Enterprise or JD Edwards EnterpriseOne applications in your environment by reviewing installed software, application directories, or system inventoryAffected if Either product is installed and reachable on the network
-
Determine PeopleTools versionLocate the PeopleTools version by checking the PS_HOME directory for a version file, or run the SQL query 'SELECT VERSION FROM PSVERSION WHERE OBJECTTYPE = 0' against the PeopleSoft databaseAffected if The version returned matches 8.48.17 or 8.49.11, or shows an unpatched PeopleTools component version
-
Verify application is network accessibleConfirm the PeopleSoft web portal or application server is exposed on the network by checking listener configurations, web server settings, or firewall rulesAffected if The PeopleSoft interface is accessible from network segments beyond the trusted internal network
-
Confirm authentication is possibleDetermine whether user accounts exist and can authenticate to the PeopleSoft system, as the vulnerability requires an authenticated attackerAffected if Standard PeopleSoft authentication is enabled and functional with valid user credentials present in the system
-
Review patch statusCheck if the April 2008 CPU or any subsequent PeopleTools patches have been applied by reviewing patch inventory or Oracle Support documentsAffected if No patches from April 2008 or later have been applied to the installed PeopleTools version
A system is affected if it runs PeopleSoft Enterprise or JD Edwards EnterpriseOne with PeopleTools version 8.48.17 or 8.49.11, or any unpatched PeopleTools version, and the application is network-accessible with authentication enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update (CPU) for April 2008 that addresses this vulnerability, or upgrade to a patched PeopleTools version. Restrict network access to PeopleSoft portals to reduce attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-2622 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2008-2622 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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