| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in TurboGears TurboGears2 and classified as problematic. This issue affects some unknown processing. This manipulation causes cryptographic issue. This vulnerability is registered as CVE-2009-5014. No exploit is available. The affected component should be upgraded.
Details
A vulnerability has been found in TurboGears TurboGears2 and classified as critical. Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a cryptographic issue vulnerability. The CWE definition for the vulnerability is CWE-310. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The default quickstart configuration of TurboGears2 (aka tg2) before 2.0.2 has a weak cookie salt, which makes it easier for remote attackers to bypass repoze.who authentication via a forged authorization cookie, a related issue to CVE-2010-3852.
The weakness was published 11/05/2010 (Website). The advisory is shared at groups.google.com. This vulnerability is known as CVE-2009-5014 since 11/05/2010. 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. MITRE ATT&CK project uses the attack technique T1600 for this issue.
Upgrading to version 1.9.7a3 eliminates this vulnerability.
Similar entry is available at VDB-55346. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 1.9.7a2
- 1.9.7a3
- 1.9.7a4
- 1.9.7b1
- 1.9.7b2
- 2.0.1
- 2.0b1
- 2.0b2
- 2.0b3
- 2.0b4
- 2.0b5
- 2.0b6
- 2.0b7
- 2.1a1
- 2.1a2
- 2.1a3
- 2.1b1
- 2.1b2
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: Cryptographic issueCWE: CWE-310
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: TurboGears2 1.9.7a3
Timeline
11/05/2010 🔍11/05/2010 🔍
11/05/2010 🔍
03/19/2015 🔍
02/08/2019 🔍
Sources
Advisory: groups.google.comStatus: Not defined
CVE: CVE-2009-5014 (🔍)
GCVE (CVE): GCVE-0-2009-5014
GCVE (VulDB): GCVE-100-55345
See also: 🔍
Entry
Created: 03/19/2015 14:37Updated: 02/08/2019 10:42
Changes: 03/19/2015 14:37 (47), 02/08/2019 10:42 (1)
Complete: 🔍
Cache ID: 216::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.