Mywebland myBloggie 2.1.1/2.1.2/2.1.3 Beta Login login.php Username sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Mywebland myBloggie 2.1.1/2.1.2/2.1.3 Beta. Affected is an unknown function of the file login.php of the component Login. This manipulation of the argument Username causes sql injection. This vulnerability is registered as CVE-2005-2838. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as critical was found in Mywebland myBloggie 2.1.1/2.1.2/2.1.3 Beta. Affected by this vulnerability is some unknown functionality of the file login.php of the component Login. The manipulation of the argument username with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in login.php in myBloggie 2.1.3-beta and earlier allows remote attackers to execute arbitrary SQL commands via the username parameter.
The weakness was published 09/07/2005 (Website). The advisory is shared at secunia.com. This vulnerability is known as CVE-2005-2838 since 09/07/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
By approaching the search of inurl:login.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (22162), SecurityFocus (BID 14739†) and Secunia (SA16699†). Similar entry is available at VDB-26501. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/05/2005 🔍09/05/2005 🔍
09/07/2005 🔍
09/07/2005 🔍
09/07/2005 🔍
03/11/2015 🔍
07/11/2018 🔍
Sources
Advisory: secunia.com⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2005-2838 (🔍)
GCVE (CVE): GCVE-0-2005-2838
GCVE (VulDB): GCVE-100-26245
X-Force: 22162 - myBloggie login.php SQL injection
SecurityFocus: 14739 - MyBloggie login.php SQL Injection Vulnerability
Secunia: 16699 - myBloggie "username" SQL Injection Vulnerability, Moderately Critical
See also: 🔍
Entry
Created: 03/11/2015 23:39Updated: 07/11/2018 04:15
Changes: 03/11/2015 23:39 (54), 07/11/2018 04:15 (7)
Complete: 🔍
Cache ID: 216:31B:103
Submit
Duplicate
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.