What is the severity of CVE-2010-3912?

CVE-2010-3912 has an unknown severity level due to the lack of detailed information regarding its impact.

How do I fix CVE-2010-3912?

To mitigate CVE-2010-3912, ensure that the supportconfig script does not store plain text passwords in configuration files.

What systems are affected by CVE-2010-3912?

CVE-2010-3912 affects SUSE Linux Enterprise 11 SP1 and SUSE Linux Enterprise 10 SP3.

What are the risks associated with CVE-2010-3912?

The risks associated with CVE-2010-3912 include the potential exposure of sensitive passwords in configuration files.

Is there a workaround for CVE-2010-3912?

A recommended workaround for CVE-2010-3912 is to manually review and secure any configuration files that may contain plaintext passwords.

Vulnerability/
CVE-2010-3912

critical

CWE

255

12/1/2011

7/8/2024

CVE-2010-3912

First published: Wed Jan 12 2011(Updated: )

The supportconfig script in supportutils in SUSE Linux Enterprise 11 SP1 and 10 SP3 does not "disguise passwords" in configuration files, which has unknown impact and attack vectors.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
SUSE Linux	=10-sp3
SUSE Linux	=11-sp1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2010-3912?
CVE-2010-3912 has an unknown severity level due to the lack of detailed information regarding its impact.
How do I fix CVE-2010-3912?
To mitigate CVE-2010-3912, ensure that the supportconfig script does not store plain text passwords in configuration files.
What systems are affected by CVE-2010-3912?
CVE-2010-3912 affects SUSE Linux Enterprise 11 SP1 and SUSE Linux Enterprise 10 SP3.
What are the risks associated with CVE-2010-3912?
The risks associated with CVE-2010-3912 include the potential exposure of sensitive passwords in configuration files.
Is there a workaround for CVE-2010-3912?
A recommended workaround for CVE-2010-3912 is to manually review and secure any configuration files that may contain plaintext passwords.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/author
agent/last-modified-date
agent/severity
agent/weakness
agent/description
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/novell
canonical/suse linux
version/suse linux/10-sp3
version/suse linux/11-sp1

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-3912?
CVE-2010-3912 has an unknown severity level due to the lack of detailed information regarding its impact.
How do I fix CVE-2010-3912?
To mitigate CVE-2010-3912, ensure that the supportconfig script does not store plain text passwords in configuration files.
What systems are affected by CVE-2010-3912?
CVE-2010-3912 affects SUSE Linux Enterprise 11 SP1 and SUSE Linux Enterprise 10 SP3.
What are the risks associated with CVE-2010-3912?
The risks associated with CVE-2010-3912 include the potential exposure of sensitive passwords in configuration files.
Is there a workaround for CVE-2010-3912?
A recommended workaround for CVE-2010-3912 is to manually review and secure any configuration files that may contain plaintext passwords.