CVE-2005-3153: SQL Injection
First published: Wed Oct 05 2005(Updated: )
login.php in myBloggie 2.1.3 beta and earlier allows remote attackers to bypass a whitelist regular expression and conduct SQL injection attacks via a username parameter with SQL after a null character, which causes the whitelist check to succeed but injects the SQL into a query string, a different vulnerability than CVE-2005-2838. NOTE: it is possible that this is actually a bug in PHP code, in which case this should not be treated as a myBloggie vulnerability.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| myWebland myBloggie | =2.1.3_beta |
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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2005-3153?
CVE-2005-3153 is classified as a high severity SQL injection vulnerability.
How do I fix CVE-2005-3153?
To fix CVE-2005-3153, upgrade to a version of myBloggie later than 2.1.3 beta that addresses this vulnerability.
What software is affected by CVE-2005-3153?
CVE-2005-3153 affects myBloggie version 2.1.3 beta and earlier.
What type of attack can be executed due to CVE-2005-3153?
CVE-2005-3153 allows remote attackers to execute SQL injection attacks through the username parameter.
What causes the vulnerability in CVE-2005-3153?
CVE-2005-3153 is caused by a flawed whitelist regular expression that allows SQL code to be injected after a null character.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/last-modified-date
- agent/severity
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/mywebland
- canonical/mywebland mybloggie
- version/mywebland mybloggie/2.1.3_beta