CVE-2013-1832: Infoleak

Published Mar 25, 2013
·
Updated

repository/webdav/lib.php in Moodle 2.x through 2.1.10, 2.2.x before 2.2.8, 2.3.x before 2.3.5, and 2.4.x before 2.4.2 includes the WebDAV password in the configuration form, which allows remote authenticated administrators to obtain sensitive information by configuring an instance.

Affected Software

40 affected componentsFixes available
composer/moodle/moodle>=2.4.0<2.4.2
2.4.2
composer/moodle/moodle>=2.3.0<2.3.5
2.3.5
composer/moodle/moodle>=2.2.0<2.2.8
2.2.8
composer/moodle/moodle>=2.0.0<=2.1.10
Moodle moodle=2.0.0
Moodle moodle=2.0.1
Moodle moodle=2.0.2
Moodle moodle=2.0.3
Moodle moodle=2.0.4
Moodle moodle=2.0.5
Moodle moodle=2.0.6
Moodle moodle=2.0.7
Moodle moodle=2.0.8
Moodle moodle=2.0.9
Moodle moodle=2.1.0
Moodle moodle=2.1.1
Moodle moodle=2.1.2
Moodle moodle=2.1.3
Moodle moodle=2.1.4
Moodle moodle=2.1.5
Moodle moodle=2.1.6
Moodle moodle=2.1.7
Moodle moodle=2.1.8
Moodle moodle=2.1.9
Moodle moodle=2.1.10
Moodle moodle=2.2.0
Moodle moodle=2.2.1
Moodle moodle=2.2.2
Moodle moodle=2.2.3
Moodle moodle=2.2.4
Moodle moodle=2.2.5
Moodle moodle=2.2.6
Moodle moodle=2.2.7
Moodle moodle=2.3.0
Moodle moodle=2.3.1
Moodle moodle=2.3.2
Moodle moodle=2.3.3
Moodle moodle=2.3.4
Moodle moodle=2.4.0
Moodle moodle=2.4.1

Event History

Mar 25, 2013
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
May 13, 2022
Advisory Published
via GitHub·01:12 AM

Frequently Asked Questions

1

What is the severity of CVE-2013-1832?

CVE-2013-1832 has a medium severity level due to its potential to expose sensitive information.

2

How do I fix CVE-2013-1832?

To fix CVE-2013-1832, upgrade to Moodle versions 2.4.2 or later, 2.3.5 or later, or 2.2.8 or later.

3

Which versions of Moodle are affected by CVE-2013-1832?

Moodle versions 2.x through 2.1.10, 2.2.x before 2.2.8, 2.3.x before 2.3.5, and 2.4.x before 2.4.2 are affected by CVE-2013-1832.

4

What is the nature of the vulnerability in CVE-2013-1832?

The vulnerability in CVE-2013-1832 allows remote authenticated administrators to obtain sensitive information by configuring an instance.

5

Can I mitigate CVE-2013-1832 without upgrading?

Mitigation of CVE-2013-1832 without upgrading is not recommended, as the best resolution is to update to a secure version.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203