Julien Plesniak LulieBlog 1.0.1/1.0.2 article_suppr.php ID access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Julien Plesniak LulieBlog 1.0.1/1.0.2. It has been rated as critical. This vulnerability affects unknown code of the file article_suppr.php. Performing a manipulation of the argument ID results in access control. This vulnerability was named CVE-2008-0329. In addition, an exploit is available.
Details
A vulnerability, which was classified as critical, was found in Julien Plesniak LulieBlog 1.0.1/1.0.2. This affects an unknown function of the file article_suppr.php. The manipulation of the argument id with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on integrity. The summary by CVE is:
LulieBlog 1.0.1 and 1.0.2 does not restrict access to (1) article_suppr.php, (2) comment_accepter.php, and (3) comment_refuser.php in Admin/, which allows remote attackers to accept comments, delete comments, and delete articles via the id parameter.
The weakness was presented 01/17/2008 (Website). The advisory is shared at milw0rm.com. This vulnerability is uniquely identified as CVE-2008-0329 since 01/17/2008. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:article_suppr.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 (39669), Exploit-DB (4912), SecurityFocus (BID 27290†) and Secunia (SA28432†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/15/2008 🔍01/15/2008 🔍
01/17/2008 🔍
01/17/2008 🔍
01/17/2008 🔍
03/16/2015 🔍
10/14/2024 🔍
Sources
Advisory: milw0rm.com⛔Status: Not defined
CVE: CVE-2008-0329 (🔍)
GCVE (CVE): GCVE-0-2008-0329
GCVE (VulDB): GCVE-100-40593
X-Force: 39669 - LulieBlog Admin directory multiple .php scripts security bypass
SecurityFocus: 27290 - LulieBlog 'id' Parameter Multiple SQL Injection Vulnerabilities
Secunia: 28432 - LulieBlog Multiple Vulnerabilities, Moderately Critical
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/16/2015 13:43Updated: 10/14/2024 12:44
Changes: 03/16/2015 13:43 (51), 09/15/2018 08:19 (11), 10/14/2024 12:44 (17)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.