| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in TIBCO tibbr 1.0.0/1.0.1/1.5.0. The affected element is an unknown function. The manipulation leads to cross site scripting. This vulnerability is traded as CVE-2011-1414. It is possible to initiate the attack remotely. There is no exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as problematic, has been found in TIBCO tibbr 1.0.0/1.0.1/1.5.0. This issue affects some unknown processing. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:
Cross-site scripting (XSS) vulnerability in the tibbr web server, as used in TIBCO tibbr 1.0.0 through 1.5.0 and tibbr Service 1.0.0 through 1.5.0, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
The weakness was shared 03/16/2011 (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2011-1414 since 03/10/2011. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
It is declared as proof-of-concept.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the databases at X-Force (66113), SecurityFocus (BID 46891†), OSVDB (71178†), Secunia (SA43765†) and SecurityTracker (ID 1025220†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.tibco.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
03/10/2011 🔍03/16/2011 🔍
03/16/2011 🔍
03/16/2011 🔍
03/16/2011 🔍
03/16/2011 🔍
03/22/2011 🔍
03/20/2015 🔍
02/09/2019 🔍
Sources
Vendor: tibco.comAdvisory: securityfocus.com⛔
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2011-1414 (🔍)
GCVE (CVE): GCVE-0-2011-1414
GCVE (VulDB): GCVE-100-56909
X-Force: 66113
SecurityFocus: 46891 - TIBCO tibbr 'HTTP Request' Cross Site Scripting Vulnerability
Secunia: 43765 - TIBCO tibbr Web Server Cross-Site Scripting Vulnerability, Less Critical
OSVDB: 71178 - TIBCO tibbr Web Server Unspecified XSS
SecurityTracker: 1025220
Vupen: ADV-2011-0687
Entry
Created: 03/20/2015 16:16Updated: 02/09/2019 10:45
Changes: 03/20/2015 16:16 (63), 02/09/2019 10:45 (1)
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.