dbcve.org
Peoplesoft And Jdedwards Product SuiteApplication · Oracle

CVE-2010-3539

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 PeopleSoft Enterprise FMS - GL 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, a different vulnerability than CVE-2010-3538.

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 PeopleSoft Enterprise FMS General Ledger (GL) component allows remote authenticated users to impact confidentiality and integrity via unknown vectors. The vulnerability affects specific bundle versions (8.9 #38, 9.0 #31, 9.1 #6) and requires authentication but can be exploited remotely over the network.

MitigationApply Oracle Critical Patch Updates for PeopleSoft to address this vulnerability. If patches are unavailable, restrict network access to PeopleSoft application ports and ensure least-privilege user access controls are enforced.

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 installation
    Check for PeopleSoft Enterprise installations on servers. Look for PeopleSoft application directories or check running services on common PeopleSoft ports (ports 80, 443, 8000, 9000).
    Affected if No PeopleSoft installation found means not affected.
  2. Determine PeopleSoft version
    Access PeopleSoft sign-in page and check the version information, or query the PeopleSoft database for version details. Look for versions 8.9, 9.0, or 9.1 specifically.
    Affected if If installed version matches 8.9, 9.0, or 9.1, the environment falls within the affected version range.
  3. Confirm FMS General Ledger component is present
    Check if the Financial Management Systems (FMS) General Ledger module is deployed or accessible in the PeopleSoft environment. This can be done via PeopleSoft Application Designer or by checking available components in the web portal.
    Affected if If the FMS General Ledger component is not installed or not accessible, the specific vulnerability may not be exploitable in that environment.
  4. Verify network exposure
    Review firewall rules and network configurations to determine if the PeopleSoft web servers are accessible from outside the internal network. Check for open ports serving PeopleSoft applications.
    Affected if If the PeopleSoft application is exposed to untrusted networks, the vulnerability could be exploited remotely as described.
  5. Confirm authentication is configured
    Review PeopleSoft user authentication settings. Check if the system is using proper authentication mechanisms (native PeopleSoft, LDAP, or external SSO).
    Affected if Since the CVE requires authenticated access, improper or disabled authentication may alter the exploitability assessment.

An environment is affected if it runs PeopleSoft Enterprise versions 8.9, 9.0, or 9.1 with the FMS General Ledger component exposed to the network and accessible to 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 to address this vulnerability. If patches are unavailable, restrict network access to PeopleSoft application ports and ensure least-privilege user access controls are enforced.

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-3539 — 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-2010-3539 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