Business Objects Webintelligence 2.7.1 Session Cookie improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Business Objects Webintelligence 2.7.1. The affected element is an unknown function of the component Session Cookie Handler. This manipulation causes improper authentication. This vulnerability is handled as CVE-2003-1249. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability has been found in Business Objects Webintelligence 2.7.1 and classified as critical. Affected by this vulnerability is some unknown processing of the component Session Cookie Handler. The manipulation with an unknown input 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:
WebIntelligence 2.7.1 uses guessable user session cookies, which allows remote attackers to hijack sessions.
The bug was discovered 01/09/2003. The weakness was released 12/31/2003 (Website). The advisory is shared at archives.neohapsis.com. This vulnerability is known as CVE-2003-1249 since 11/16/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 356 days. During that time the estimated underground price was around $0-$5k.
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 (11026), SecurityFocus (BID 6569†), OSVDB (59816†), Secunia (SA7846†) and SecurityTracker (ID 1005906†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
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: Improper authenticationCWE: CWE-287
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/09/2003 🔍01/09/2003 🔍
01/09/2003 🔍
12/31/2003 🔍
12/31/2003 🔍
11/16/2005 🔍
08/22/2014 🔍
07/16/2024 🔍
Sources
Advisory: archives.neohapsis.comStatus: Confirmed
CVE: CVE-2003-1249 (🔍)
GCVE (CVE): GCVE-0-2003-1249
GCVE (VulDB): GCVE-100-21181
X-Force: 11026
SecurityFocus: 6569 - Business Objects WebIntelligence Application Session Hijacking Vulnerability
Secunia: 7846
OSVDB: 59816 - Business Objects - WebIntelligence - Application Session Hijacking Issue
SecurityTracker: 1005906
Entry
Created: 08/22/2014 16:10Updated: 07/16/2024 05:38
Changes: 08/22/2014 16:10 (56), 09/05/2019 16:23 (3), 07/16/2024 05:38 (17)
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.