OnShift TurboGears 18.104.22.168 HTTP Header controllers.py response splitting
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability classified as critical has been found in OnShift TurboGears 22.214.171.124. 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 software receives data from an upstream component, but 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 126.96.36.199 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.
CVSSv3VulDB Meta Base Score: 7.5
VulDB 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): 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
NVD Base Score: 🔒
ExploitingClass: Response splitting
CWE: CWE-113 / CWE-93 / CWE-74
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Upgrade: TurboGears 188.8.131.52
Timeline02/02/2023 Advisory disclosed
02/02/2023 +0 days CVE reserved
02/02/2023 +0 days VulDB entry created
03/04/2023 +30 days VulDB last update
CVE: CVE-2019-25101 (🔒)
EntryCreated: 02/02/2023 09:03 PM
Updated: 03/04/2023 09:15 AM
Changes: 02/02/2023 09:03 PM (45), 03/04/2023 09:11 AM (2), 03/04/2023 09:15 AM (28)
Interested in the pricing of exploits?
See the underground prices here!
No comments yet. Languages: en.
Please log in to comment.