| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Trustwave WebDefend 2.0/3.0. This affects an unknown part. Performing a manipulation results in credentials management. This vulnerability is known as CVE-2011-0756. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Trustwave WebDefend 2.0/3.0. It has been classified as critical. This affects an unknown functionality. The manipulation with an unknown input leads to a credentials management vulnerability. CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality. The summary by CVE is:
The application server in Trustwave WebDefend Enterprise before 5.0 uses hardcoded console credentials, which makes it easier for remote attackers to read security-event data by using the remote console GUI to connect to the management port.
The weakness was published 05/04/2011 (Website). The advisory is shared at trustwave.com. This vulnerability is uniquely identified as CVE-2011-0756 since 02/02/2011. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
Upgrading to version 3.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityTracker (ID 1025447†). Similar entry is available at VDB-57356. 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: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Credentials managementCWE: CWE-255
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: WebDefend 3.0
Timeline
02/02/2011 🔍04/27/2011 🔍
05/04/2011 🔍
05/04/2011 🔍
03/23/2015 🔍
02/09/2019 🔍
Sources
Advisory: trustwave.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2011-0756 (🔍)
GCVE (CVE): GCVE-0-2011-0756
GCVE (VulDB): GCVE-100-57345
SecurityTracker: 1025447
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 02/09/2019 11:03
Changes: 03/23/2015 16:50 (47), 02/09/2019 11:03 (6)
Complete: 🔍
Cache ID: 216:D38: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.