First published: Wed Aug 28 2013(Updated: )
The Login Security module 6.x-1.x before 6.x-1.3 and 7.x-1.x before 7.x-1.3 for Drupal, when using the login delay option, allows remote attackers to cause a denial of service (CPU consumption) via a large number of failed login attempts.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Login Security Project Login Security | =6.x-1.0 | |
Login Security Project Login Security | =6.x-1.0-beta1 | |
Login Security Project Login Security | =6.x-1.0-rc1 | |
Login Security Project Login Security | =6.x-1.1 | |
Login Security Project Login Security | =6.x-1.2 | |
Login Security Project Login Security | =6.x-1.3 | |
Login Security Project Login Security | =6.x-1.x-dev | |
Login Security Project Login Security | =7.x-1.0 | |
Login Security Project Login Security | =7.x-1.1 | |
Login Security Project Login Security | =7.x-1.2 | |
Login Security Project Login Security | =7.x-1.x-dev | |
Drupal Drupal |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-2197 has a medium severity rating due to its potential for causing denial of service through excessive login attempts.
To fix CVE-2013-2197, upgrade the Login Security module to version 6.x-1.3 or 7.x-1.3 or later.
CVE-2013-2197 affects users of the Login Security module versions prior to 6.x-1.3 and 7.x-1.3 on Drupal.
Exploitation of CVE-2013-2197 can lead to increased CPU consumption due to numerous failed login attempts.
Yes, CVE-2013-2197 allows remote attackers to exploit the vulnerability without requiring local access.