CVE-2010-3536
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 SCM component in Oracle PeopleSoft and JDEdwards Suite 8.9 Bundle #38, 9.0 Bundle #31, and 9.1 Bundle #6 allows remote authenticated users to affect confidentiality and integrity via unknown vectors.
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 confidenceThis is an authenticated vulnerability in Oracle PeopleSoft Enterprise Supply Chain Management (SCM) affecting versions 8.9 Bundle #38, 9.0 Bundle #31, and 9.1 Bundle #6. Remote authenticated users can impact confidentiality and integrity through unspecified vectors in the SCM component.
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.9= 9.0= 9.1CVSS 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
- None
AV:N/AC:L/Au:S/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 Enterprise SCM versionAccess PeopleSoft Application Designer or use SQL query on PSVERSION table to retrieve the current PeopleTools version and bundle number installedAffected if The installed version matches 8.9 (any bundle), 9.0 (any bundle), or 9.1 (any bundle) and is below the fixed Bundle #38 for 8.9, Bundle #31 for 9.0, or Bundle #6 for 9.1
-
Confirm SCM component is deployedCheck PeopleSoft Application Designer or navigation menus for presence of Supply Chain Management modules such as Inventory Management, Purchasing, or Order ManagementAffected if SCM component is installed and the version matches the vulnerable ranges listed above
-
Verify PeopleSoft web entry points are accessibleConfirm the PeopleSoft HTTP/HTTPS listeners are active and remote network access to PeopleSoft ports (typically 80, 443, or custom ports) is possibleAffected if Remote unauthenticated or authenticated network access to the PeopleSoft web interface is possible and the SCM version falls within the affected version ranges
A system is affected if it runs Oracle PeopleSoft Enterprise SCM versions 8.9, 9.0, or 9.1 with bundle numbers below the fixed thresholds (8.9 Bundle #38, 9.0 Bundle #31, 9.1 Bundle #6) and has the SCM component enabled with remote accessibility.
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 the Oracle Critical Patch Update from October 2010 that addresses this vulnerability. Prior to patch deployment, perform complete backups and test in a non-production environment to validate compatibility.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3536 — 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-2010-3536 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