Peoplesoft And Jdedwards Product SuiteApplication · Oracle

CVE-2010-3525

MEDIUM · 5.5 CVSS v2.0 Published 2010-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable 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 (1) PeopleSoft Enterprise FMS, (2) SCM, (3) EPM, (4) CRM, and (5) Campus Solutions components in Oracle PeopleSoft and JDEdwards Suite 8.9, 9.0, and 9.1 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 confidence

Unspecified vulnerability in Oracle PeopleSoft and JDEdwards Suite versions 8.9, 9.0, and 9.1 affecting FMS, SCM, EPM, CRM, and Campus Solutions components. Allows remote authenticated users to impact confidentiality and integrity via unknown attack vectors.

MitigationApply Oracle Critical Patch Updates for PeopleSoft and JDEdwards Suite. Restrict network access to PeopleSoft portals to trusted users only and ensure principle of least privilege for authenticated accounts.

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
Peoplesoft And Jdedwards Product SuiteApplication
Affected:= 8.9= 9.0= 9.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify PeopleSoft/JDEdwards product version
    Access the PeopleSoft About page (usually via Help > About in the application) or use the PSADMIN utility to query the installed version. Check the version information displayed in the system.
    Affected if The installed version is exactly 8.9, 9.0, or 9.1
  2. Confirm installed components
    Review the installed application modules through the PeopleSoft Application Designer or system configuration. Check which product families are licensed and deployed.
    Affected if Any of the following components are installed: FMS (Financial Management Systems), SCM (Supply Chain Management), EPM (Enterprise Performance Management), CRM (Customer Relationship Management), or Campus Solutions
  3. Verify remote access is enabled
    Check the PeopleSoft web server configuration (webservic.properties or psappsrv.cfg) for internet-facing bindings. Review the HTTP listener configuration and the Psigy.xml file for exposed endpoints.
    Affected if The PeopleSoft application is accessible remotely over HTTP/HTTPS to untrusted networks rather than being isolated on an internal network
  4. Check authentication configuration
    Review the PeopleSoft directory structure and access control settings in PSADMIN or the web profile configuration. Verify that remote user authentication is permitted.
    Affected if Remote authenticated users can access the application (as opposed to local-only access with strong network segmentation)

Your environment is affected if you are running PeopleSoft or JDEdwards version 8.9, 9.0, or 9.1 with any of the FMS, SCM, EPM, CRM, or Campus Solutions components installed and accessible to remote authenticated users.

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 Updates for PeopleSoft and JDEdwards Suite. Restrict network access to PeopleSoft portals to trusted users only and ensure principle of least privilege for authenticated accounts.

Fix this in Peoplesoft And Jdedwards Product Suite Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-3525 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-3525 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