low
3.5
CWE
200
Advisory Published
Advisory Published
Updated

CVE-2013-1835: Infoleak

First published: Mon Mar 25 2013(Updated: )

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 allows remote authenticated administrators to obtain sensitive information from the external repositories of arbitrary users by leveraging the login_as feature.

Credit: secalert@redhat.com secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
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.0.0<2.2.8
2.2.8
Moodle=2.0.0
Moodle=2.0.1
Moodle=2.0.2
Moodle=2.0.3
Moodle=2.0.4
Moodle=2.0.5
Moodle=2.0.6
Moodle=2.0.7
Moodle=2.0.8
Moodle=2.0.9
Moodle=2.1.0
Moodle=2.1.1
Moodle=2.1.2
Moodle=2.1.3
Moodle=2.1.4
Moodle=2.1.5
Moodle=2.1.6
Moodle=2.1.7
Moodle=2.1.8
Moodle=2.1.9
Moodle=2.1.10
Moodle=2.2.0
Moodle=2.2.1
Moodle=2.2.2
Moodle=2.2.3
Moodle=2.2.4
Moodle=2.2.5
Moodle=2.2.6
Moodle=2.2.7
Moodle=2.3.0
Moodle=2.3.1
Moodle=2.3.2
Moodle=2.3.3
Moodle=2.3.4
Moodle=2.4.0
Moodle=2.4.1

Remedy

http://git.moodle.org/gw?p=moodle.git&a=search&h=HEAD&st=commit&s=MDL-36426

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2013-1835?

    CVE-2013-1835 is classified as a moderate severity vulnerability due to its potential for unauthorized access to sensitive user information.

  • How do I fix CVE-2013-1835?

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

  • Who is affected by CVE-2013-1835?

    CVE-2013-1835 affects Moodle versions 2.x up to 2.4.1, specifically allowing authenticated administrators to access external repositories.

  • What are the implications of CVE-2013-1835?

    The implications of CVE-2013-1835 include potential exposure of sensitive information from external repositories of users.

  • Is there a specific workaround for CVE-2013-1835?

    There is no specific workaround for CVE-2013-1835; the recommended solution is to update to the secured versions.

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