What is the severity of CVE-2010-3547?

The severity of CVE-2010-3547 is considered to affect confidentiality and integrity of the affected systems.

How do I fix CVE-2010-3547?

To fix CVE-2010-3547, apply the appropriate patches provided by Oracle for the affected PeopleSoft FMS ESA - EX components.

Which versions of Oracle PeopleSoft are affected by CVE-2010-3547?

CVE-2010-3547 affects Oracle PeopleSoft versions 8.9 Bundle #38, 9.0 Bundle #31, and 9.1 Bundle #6.

What type of attacks can CVE-2010-3547 enable?

CVE-2010-3547 can potentially enable remote authenticated users to compromise confidentiality and integrity of the system.

Is there a workaround for CVE-2010-3547?

Currently, the recommended action for CVE-2010-3547 is to apply the available patches rather than relying on workarounds.

Vulnerability/
CVE-2010-3547

medium

5.5

CWE

14/10/2010

11/11/2010

CVE-2010-3547

First published: Thu Oct 14 2010(Updated: )

Unspecified vulnerability in the PeopleSoft FMS ESA - EX 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.

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle PeopleSoft and JD Edwards Product Suite	=8.9-bundle38
Oracle PeopleSoft and JD Edwards Product Suite	=9.0-bundle31
Oracle PeopleSoft and JD Edwards Product Suite	=9.1-bundle6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2010-3547?
The severity of CVE-2010-3547 is considered to affect confidentiality and integrity of the affected systems.
How do I fix CVE-2010-3547?
To fix CVE-2010-3547, apply the appropriate patches provided by Oracle for the affected PeopleSoft FMS ESA - EX components.
Which versions of Oracle PeopleSoft are affected by CVE-2010-3547?
CVE-2010-3547 affects Oracle PeopleSoft versions 8.9 Bundle #38, 9.0 Bundle #31, and 9.1 Bundle #6.
What type of attacks can CVE-2010-3547 enable?
CVE-2010-3547 can potentially enable remote authenticated users to compromise confidentiality and integrity of the system.
Is there a workaround for CVE-2010-3547?
Currently, the recommended action for CVE-2010-3547 is to apply the available patches rather than relying on workarounds.

agent/references
agent/type
agent/first-publish-date
agent/last-modified-date
agent/severity
agent/weakness
agent/author
agent/softwarecombine
agent/tags
agent/description
agent/event
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/oracle
canonical/oracle peoplesoft and jd edwards product suite
version/oracle peoplesoft and jd edwards product suite/8.9-bundle38
version/oracle peoplesoft and jd edwards product suite/9.0-bundle31
version/oracle peoplesoft and jd edwards product suite/9.1-bundle6

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2010-3547?
The severity of CVE-2010-3547 is considered to affect confidentiality and integrity of the affected systems.
How do I fix CVE-2010-3547?
To fix CVE-2010-3547, apply the appropriate patches provided by Oracle for the affected PeopleSoft FMS ESA - EX components.
Which versions of Oracle PeopleSoft are affected by CVE-2010-3547?
CVE-2010-3547 affects Oracle PeopleSoft versions 8.9 Bundle #38, 9.0 Bundle #31, and 9.1 Bundle #6.
What type of attacks can CVE-2010-3547 enable?
CVE-2010-3547 can potentially enable remote authenticated users to compromise confidentiality and integrity of the system.
Is there a workaround for CVE-2010-3547?
Currently, the recommended action for CVE-2010-3547 is to apply the available patches rather than relying on workarounds.