medium
5.5
CWE
264
Advisory Published
Updated

CVE-2010-3092

First published: Tue Sep 21 2010(Updated: )

The upload module in Drupal 5.x before 5.23 and 6.x before 6.18 does not properly support case-insensitive filename handling in a database configuration, which allows remote authenticated users to bypass the intended restrictions on downloading a file by uploading a different file with a similar name.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
Drupal=5.10
Drupal=5.4
Drupal=5.17
Drupal=5.13
Drupal=5.12
Drupal=5.2
Drupal=5.7
Drupal=5.0-rc2
Drupal=5.16
Drupal=5.0
Drupal=5.15
Drupal=5.18
Drupal=5.21
Drupal=5.22
Drupal=5.0-rc1
Drupal=5.0-dev
Drupal=5.6
Drupal=5.0-beta2
Drupal=5.1
Drupal=5.19
Drupal=5.5
Drupal=5.14
Drupal=5.9
Drupal=5.8
Drupal=5.3
Drupal=5.0-beta1
Drupal=5.11
Drupal=5.20
Drupal=6.0-beta2
Drupal=6.0-rc2
Drupal=6.2
Drupal=6.14
Drupal=6.13
Drupal=6.0-dev
Drupal=6.0-beta4
Drupal=6.12
Drupal=6.0-rc3
Drupal=6.0-rc4
Drupal=6.4
Drupal=6.11
Drupal=6.0-beta1
Drupal=6.7
Drupal=6.8
Drupal=6.1
Drupal=6.17
Drupal=6.5
Drupal=6.10
Drupal=6.6
Drupal=6.0
Drupal=6.15
Drupal=6.0-beta3
Drupal=6.16
Drupal=6.3
Drupal=6.0-rc1
Drupal=6.9

Remedy

http://drupal.org/node/880476

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-2010-3092?

    CVE-2010-3092 is classified as a medium severity vulnerability affecting specific versions of Drupal.

  • How do I fix CVE-2010-3092?

    To fix CVE-2010-3092, upgrade Drupal to version 5.23 or 6.18 or later, as these versions include the necessary security patches.

  • Who is affected by CVE-2010-3092?

    CVE-2010-3092 affects Drupal versions 5.x before 5.23 and 6.x before 6.18.

  • What kind of attack is possible due to CVE-2010-3092?

    CVE-2010-3092 allows remote authenticated users to bypass file restrictions by uploading files with similar names.

  • Is there any workaround for CVE-2010-3092 before patching?

    There are no specific workarounds for CVE-2010-3092, so upgrading to a patched version is recommended.

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