What is the severity of CVE-2001-1537?

CVE-2001-1537 has a high severity level due to the exposure of cleartext usernames and passwords in cookies.

How do I fix CVE-2001-1537?

To fix CVE-2001-1537, update to a version of TWIG webmail later than 2.7.4 that has addressed this security issue.

Who is affected by CVE-2001-1537?

CVE-2001-1537 affects users of TWIG webmail versions 2.7.4 and earlier, as well as Symfony Twig versions up to 2.7.4.

What is the impact of CVE-2001-1537?

The impact of CVE-2001-1537 could allow attackers to gain unauthorized access to user accounts by stealing authentication information.

Is there a workaround for CVE-2001-1537?

A temporary workaround for CVE-2001-1537 includes disabling cookies or implementing alternative secure authentication methods.

Vulnerability/
CVE-2001-1537

high

7.5

CWE

NVD-CWE-Other 312

31/12/2001

14/7/2005

8/8/2024

CVE-2001-1537

First published: Mon Dec 31 2001(Updated: )

The default "basic" security setting' in config.php for TWIG webmail 2.7.4 and earlier stores cleartext usernames and passwords in cookies, which could allow attackers to obtain authentication information and gain privileges.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
TWIG webmail	<=2.7.4
symfony Twig	<=2.7.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2001-1537?
CVE-2001-1537 has a high severity level due to the exposure of cleartext usernames and passwords in cookies.
How do I fix CVE-2001-1537?
To fix CVE-2001-1537, update to a version of TWIG webmail later than 2.7.4 that has addressed this security issue.
Who is affected by CVE-2001-1537?
CVE-2001-1537 affects users of TWIG webmail versions 2.7.4 and earlier, as well as Symfony Twig versions up to 2.7.4.
What is the impact of CVE-2001-1537?
The impact of CVE-2001-1537 could allow attackers to gain unauthorized access to user accounts by stealing authentication information.
Is there a workaround for CVE-2001-1537?
A temporary workaround for CVE-2001-1537 includes disabling cookies or implementing alternative secure authentication methods.

collector/nvd-historical
collector/nvd-index
agent/type
agent/first-publish-date
agent/references
agent/author
agent/weakness
agent/severity
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/twig
canonical/twig webmail
version/twig webmail/2.7.4
vendor/symfony
canonical/symfony twig
version/symfony twig/2.7.4

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-1537?
CVE-2001-1537 has a high severity level due to the exposure of cleartext usernames and passwords in cookies.
How do I fix CVE-2001-1537?
To fix CVE-2001-1537, update to a version of TWIG webmail later than 2.7.4 that has addressed this security issue.
Who is affected by CVE-2001-1537?
CVE-2001-1537 affects users of TWIG webmail versions 2.7.4 and earlier, as well as Symfony Twig versions up to 2.7.4.
What is the impact of CVE-2001-1537?
The impact of CVE-2001-1537 could allow attackers to gain unauthorized access to user accounts by stealing authentication information.
Is there a workaround for CVE-2001-1537?
A temporary workaround for CVE-2001-1537 includes disabling cookies or implementing alternative secure authentication methods.