weblabyrinth 0.3.1 labyrinth.inc.php Labyrinth sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in weblabyrinth 0.3.1. Affected by this issue is the function Labyrinth of the file labyrinth.inc.php. Performing a manipulation results in sql injection.
This vulnerability is identified as CVE-2011-10002. There is not any exploit available.
It is advisable to upgrade the affected component.
Details
A vulnerability classified as critical has been found in weblabyrinth 0.3.1. This affects the function Labyrinth of the file labyrinth.inc.php. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was released 02/06/2023. The advisory is shared at code.google.com. This vulnerability is uniquely identified as CVE-2011-10002. 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:labyrinth.inc.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 0.3.2 eliminates this vulnerability. The upgrade is hosted for download at storage.googleapis.com. Applying the patch 60793fd8c8c4759596d3510641e96ea40e7f60e9 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. The advisory contains the following remark:
Fixed SQLi bug described in https://code.google.com/p/weblabyrinth/issues/detail?id=1
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 5.5
CNA Vector (VulDB): 🔍
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: weblabyrinth 0.3.2
Patch: 60793fd8c8c4759596d3510641e96ea40e7f60e9
Timeline
02/06/2023 🔍02/06/2023 🔍
02/06/2023 🔍
03/05/2023 🔍
Sources
Advisory: 60793fd8c8c4759596d3510641e96ea40e7f60e9Status: Confirmed
CVE: CVE-2011-10002 (🔍)
GCVE (CVE): GCVE-0-2011-10002
GCVE (VulDB): GCVE-100-220221
Entry
Created: 02/06/2023 14:11Updated: 03/05/2023 10:05
Changes: 02/06/2023 14:11 (43), 03/05/2023 10:03 (3), 03/05/2023 10:05 (28)
Complete: 🔍
Cache ID: 216::103
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.