| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OpenJournal up to 2.0 5. It has been classified as problematic. This impacts an unknown function of the file oj.cgi. This manipulation of the argument uid with the input 0 causes improper authentication.
This vulnerability is registered as CVE-2004-0261. Furthermore, an exploit is available.
Details
A vulnerability has been found in OpenJournal up to 2.0 5 and classified as critical. Affected by this vulnerability is an unknown code block of the file oj.cgi. The manipulation of the argument uid with the input value 0 leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
oj.cgi in OpenJournal 2.0 through 2.0.5 allows remote attackers to bypass authentication and access the control panel via a 0 in the uid parameter.
The weakness was published 02/06/2004 by Tri Huynh (Website). The advisory is shared at marc.theaimsgroup.com. This vulnerability is known as CVE-2004-0261. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
After even before and not, there has been an exploit disclosed. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
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 (15069), Exploit-DB (23659), SecurityFocus (BID 9598†), OSVDB (3872†) and Secunia (SA10808†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.3
VulDB Base Score: 9.8
VulDB Temp Score: 9.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: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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
02/06/2004 🔍02/06/2004 🔍
02/06/2004 🔍
02/09/2004 🔍
02/09/2004 🔍
11/23/2004 🔍
04/14/2015 🔍
09/14/2024 🔍
Sources
Advisory: marc.theaimsgroup.comResearcher: Tri Huynh
Status: Not defined
Confirmation: 🔍
CVE: CVE-2004-0261 (🔍)
GCVE (CVE): GCVE-0-2004-0261
GCVE (VulDB): GCVE-100-22405
X-Force: 15069 - OpenJournal uid could allow an attacker administrative access
SecurityFocus: 9598 - OpenJournal Authentication Bypassing Vulnerability
Secunia: 10808 - OpenJournal Authentication Bypass Vulnerability, Moderately Critical
OSVDB: 3872 - OpenJournal oj.cgi uid Parameter Authentication Bypass
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 04/14/2015 13:23Updated: 09/14/2024 19:03
Changes: 04/14/2015 13:23 (56), 06/22/2018 07:40 (8), 09/14/2024 19:03 (21)
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.