dbcve.org
Peoplesoft And Jdedwards Product SuiteApplication · Oracle

CVE-2010-3538

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-3539.

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 the PeopleSoft Enterprise FMS General Ledger (GL) component affecting versions 8.9 Bundle #38, 9.0 Bundle #31, and 9.1 Bundle #6. The flaw allows remote authenticated users to impact confidentiality and integrity via unknown attack vectors, requiring user authentication but exploitable over the network.

MitigationApply the relevant Oracle Critical Patch Update for 2010 that addresses this vulnerability in the PeopleSoft Enterprise FMS GL component. Until patching is feasible, restrict network access to PeopleSoft applications to trusted users only and monitor for unusual GL transactions or data access patterns.

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 installed PeopleSoft Enterprise version
    Access the PeopleSoft Enterprise administration console or version information page. Look for the exact version number and bundle patch level (e.g., 8.9, 9.0, or 9.1) and note the Bundle number applied.
    Affected if The installed version is 8.9 Bundle #38 or lower, 9.0 Bundle #31 or lower, or 9.1 Bundle #6 or lower.
  2. Confirm the FMS General Ledger component is present
    Check the PeopleSoft application modules list or component registry to verify that the Financial Management Systems (FMS) General Ledger (GL) module is installed and enabled in the environment.
    Affected if The FMS GL component is present and active in the PeopleSoft installation.
  3. Verify network accessibility of PeopleSoft web tier
    Determine if the PeopleSoft application server web tier (PIA - PeopleSoft Internet Architecture) is reachable over the network. Check firewall rules, load balancer configurations, or network ACLs that permit access to the PeopleSoft HTTP/HTTPS ports.
    Affected if The PeopleSoft application is network-accessible from untrusted networks or external IP addresses.
  4. Confirm user authentication is required for access
    Review the PeopleSoft authentication configuration to ensure that valid user credentials are required to access the FMS GL component. Check if anonymous access or guest accounts are enabled for GL-related pages.
    Affected if User authentication is not properly enforced or if anonymous/guest access is permitted to GL functions.
  5. Review recent GL transaction logs for anomalies
    Examine PeopleSoft audit logs, GL transaction logs, and security monitoring reports for unusual data access patterns, unauthorized data exports, or suspicious journal entries originating from authenticated user sessions.
    Affected if Unusual or unauthorized GL activity is observed in logs or audit trails.

A user is affected if their PeopleSoft Enterprise installation runs version 8.9 Bundle #38 or lower, 9.0 Bundle #31 or lower, or 9.1 Bundle #6 or lower, has the FMS GL component enabled, and is accessible over the network 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 the relevant Oracle Critical Patch Update for 2010 that addresses this vulnerability in the PeopleSoft Enterprise FMS GL component. Until patching is feasible, restrict network access to PeopleSoft applications to trusted users only and monitor for unusual GL transactions or data access patterns.

Fix this in Peoplesoft And Jdedwards Product Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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