CVE-2009-1013
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 Enterprise PeopleTools component in Oracle PeopleSoft Enterprise and JD Edwards EnterpriseOne 8.49.19 allows remote attackers to affect confidentiality and integrity via unknown vectors, a different vulnerability than CVE-2009-1014.
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 confidenceUnspecified vulnerability in PeopleSoft Enterprise PeopleTools affecting Oracle PeopleSoft Enterprise and JD Edwards EnterpriseOne version 8.49.19. Allows remote attackers to impact confidentiality and integrity via unknown vectors. Distinct from CVE-2009-1014.
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.49.19all 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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/A:N
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 installationLocate PeopleSoft Enterprise or JD Edwards EnterpriseOne installation directories. Common paths include $PS_HOME for PeopleSoft and $JDE_HOME for JD Edwards. Check for PeopleSoft Process Scheduler, web servers (PIA - PeopleSoft Internet Architecture), or application server domains.Affected if Any PeopleSoft Enterprise or JD Edwards EnterpriseOne installation is present
-
Determine PeopleSoft Enterprise versionCheck the version file in the PS_HOME directory or look at the About PeopleSoft page accessible via the PeopleSoft Internet Architecture login page. The version is typically displayed in the system information or can be retrieved via SQL query against the PSVERSION table.Affected if Any version of Oracle PeopleSoft Enterprise is found (all versions affected)
-
Determine JD Edwards EnterpriseOne versionCheck the JD Edwards EnterpriseOne deployment directory or run the 'jde.ini' or 'jde.log' files for version information. The version number 8.49.19 should be visible in the system configuration.Affected if Version 8.49.19 of JD Edwards EnterpriseOne is found
-
Assess network exposure of PeopleSoft web interfacesDetermine if the PeopleSoft Internet Architecture (PIA) web server or any PeopleSoft web services are accessible from untrusted networks. Check firewall rules and load balancer configurations that expose the PeopleSoft web ports (typically 80, 443, or custom ports).Affected if PeopleSoft web interfaces are reachable from remote/untrusted networks
A user is affected if they have any version of Oracle PeopleSoft Enterprise installed, or specifically version 8.49.19 of JD Edwards EnterpriseOne, with network-accessible PeopleSoft components.
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) from April 2009 or later. Until patched, restrict network access to PeopleSoft servers and implement principle of least privilege on affected endpoints.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1013 — 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-2009-1013 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