What is the severity of CVE-2001-1371?

CVE-2001-1371 is considered to have a high severity due to the potential for unauthorized application deployment.

How do I fix CVE-2001-1371?

To fix CVE-2001-1371, it is recommended to disable SOAP services or configure access controls to restrict anonymous user access.

What platforms are affected by CVE-2001-1371?

CVE-2001-1371 specifically affects Oracle Application Server version 1.0.2.

Can CVE-2001-1371 be exploited remotely?

Yes, CVE-2001-1371 can be exploited remotely by anonymous users to deploy applications due to the default configuration.

Is there a patch available for CVE-2001-1371?

There is no specific patch available for CVE-2001-1371, but changing the default configuration is recommended to mitigate the risk.

Vulnerability/
CVE-2001-1371

high

7.5

CWE

264

6/2/2002

2/4/2003

8/8/2024

CVE-2001-1371

First published: Wed Feb 06 2002(Updated: )

The default configuration of Oracle Application Server 9iAS 1.0.2.2 enables SOAP and allows anonymous users to deploy applications by default via urn:soap-service-manager and urn:soap-provider-manager.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Oracle Application Server	=1.0.2

Remedy

http://www.cert.org/advisories/CA-2002-08.html

Remedy

http://www.securityfocus.com/bid/4289

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2001-1371?
CVE-2001-1371 is considered to have a high severity due to the potential for unauthorized application deployment.
How do I fix CVE-2001-1371?
To fix CVE-2001-1371, it is recommended to disable SOAP services or configure access controls to restrict anonymous user access.
What platforms are affected by CVE-2001-1371?
CVE-2001-1371 specifically affects Oracle Application Server version 1.0.2.
Can CVE-2001-1371 be exploited remotely?
Yes, CVE-2001-1371 can be exploited remotely by anonymous users to deploy applications due to the default configuration.
Is there a patch available for CVE-2001-1371?
There is no specific patch available for CVE-2001-1371, but changing the default configuration is recommended to mitigate the risk.

collector/nvd-historical
collector/nvd-index
agent/weakness
agent/type
agent/softwarecombine
agent/first-publish-date
agent/remedy
collector/mitre-cve
source/MITRE
agent/references
agent/severity
agent/last-modified-date
agent/author
agent/description
agent/event
agent/tags
agent/source
vendor/oracle
canonical/oracle application server
version/oracle application server/1.0.2

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-2001-1371?
CVE-2001-1371 is considered to have a high severity due to the potential for unauthorized application deployment.
How do I fix CVE-2001-1371?
To fix CVE-2001-1371, it is recommended to disable SOAP services or configure access controls to restrict anonymous user access.
What platforms are affected by CVE-2001-1371?
CVE-2001-1371 specifically affects Oracle Application Server version 1.0.2.
Can CVE-2001-1371 be exploited remotely?
Yes, CVE-2001-1371 can be exploited remotely by anonymous users to deploy applications due to the default configuration.
Is there a patch available for CVE-2001-1371?
There is no specific patch available for CVE-2001-1371, but changing the default configuration is recommended to mitigate the risk.