OnShift TurboGears 1.0.11.10 HTTP Header controllers.py response splitting
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.4 | $0-$5k | 0.03 |
A vulnerability classified as critical has been found in OnShift TurboGears 1.0.11.10. This affects an unknown function of the file turbogears/controllers.py of the component HTTP Header Handler. The manipulation with an unknown input leads to a response splitting vulnerability. CWE is classifying the issue as CWE-113. The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was shared 02/02/2023 as 18. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2019-25101. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 1.0.11.11 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch f68bbaba47f4474e1da553aa51564a73e1d92a84 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. The advisory contains the following remark:
There was a Header Injection issue (remember HTTP is a text protocol and new lines matter). Basically you could inject a header or even the text with certain parameters.
The entries VDB-254778, VDB-255837, VDB-256512 and VDB-258341 are related to this item.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 6.3
CNA Vector (VulDB): 🔍
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: Response splittingCWE: CWE-113 / CWE-93 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
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: TurboGears 1.0.11.11
Patch: f68bbaba47f4474e1da553aa51564a73e1d92a84
Timeline
02/02/2023 🔍02/02/2023 🔍
02/02/2023 🔍
03/04/2023 🔍
Sources
Advisory: 18Status: Confirmed
CVE: CVE-2019-25101 (🔍)
See also: 🔍
Entry
Created: 02/02/2023 21:03Updated: 03/04/2023 09:15
Changes: 02/02/2023 21:03 (45), 03/04/2023 09:11 (2), 03/04/2023 09:15 (28)
Complete: 🔍
Cache ID: 18:8F3:103
No comments yet. Languages: en.
Please log in to comment.