| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OTRS. It has been rated as critical. This affects an unknown part of the component Access Restriction. The manipulation leads to access control. This vulnerability is documented as CVE-2008-7279. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in OTRS (Service Management Software). It has been rated as critical. This issue affects an unknown function of the component Access Restriction. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The CustomerInterface component in Open Ticket Request System (OTRS) before 2.2.8 allows remote authenticated users to bypass intended access restrictions and access tickets of arbitrary customers via unspecified vectors.
The weakness was released 03/18/2011 (Website). The advisory is shared at source.otrs.org. The identification of this vulnerability is CVE-2008-7279. The exploitation is known to be easy. The attack may be initiated remotely. The successful exploitation requires a simple authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 0.5 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (66482) and Vulnerability Center (SBV-30784†). Entries connected to this vulnerability are available at VDB-56879, VDB-56878, VDB-56877 and VDB-56875. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 0.5
- 1.0.0
- 1.0.1
- 1.0.2
- 1.1.0
- 1.1.1
- 1.1.2
- 1.1.3
- 1.1.4
- 1.2.0
- 1.2.1
- 1.2.2
- 1.2.3
- 1.2.4
- 1.3.0
- 1.3.1
- 1.3.2
- 1.3.3
- 2.0.0
- 2.0.1
- 2.0.2
- 2.0.3
- 2.0.4
- 2.0.5
- 2.1.0
- 2.1.1
- 2.1.2
- 2.1.3
- 2.1.4
- 2.1.5
- 2.1.6
- 2.1.7
- 2.1.8
- 2.1.9
- 2.2.0
- 2.2.1
- 2.2.2
- 2.2.3
- 2.2.4
- 2.2.5
- 2.2.6
- 2.2.7
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
OpenVAS ID: 841190
OpenVAS Name: OTRS CustomerInterface Restriction Bypass Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: OTRS 0.5
Timeline
03/16/2011 🔍03/18/2011 🔍
03/18/2011 🔍
03/18/2011 🔍
04/04/2011 🔍
03/20/2015 🔍
10/19/2021 🔍
Sources
Advisory: source.otrs.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2008-7279 (🔍)
GCVE (CVE): GCVE-0-2008-7279
GCVE (VulDB): GCVE-100-56861
X-Force: 66482
Vulnerability Center: 30784 - Open Ticket Request System before 2.2.8 CustomerInterface component Access Restrictions Bypass, Medium
See also: 🔍
Entry
Created: 03/20/2015 16:16Updated: 10/19/2021 19:23
Changes: 03/20/2015 16:16 (49), 03/20/2017 09:27 (10), 10/19/2021 19:23 (4)
Complete: 🔍
Cache ID: 216:693: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.