| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Web2py up to 2.14.1. It has been declared as problematic. This vulnerability affects unknown code of the file examples/simple_examples/status. Such manipulation as part of Request leads to information disclosure. This vulnerability is traded as CVE-2016-3954. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Web2py up to 2.14.1 and classified as problematic. Affected by this issue is some unknown processing of the file examples/simple_examples/status. The manipulation as part of a Request leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. CVE summarizes:
web2py before 2.14.2 allows remote attackers to obtain the session_cookie_key value via a direct request to examples/simple_examples/status. NOTE: this issue can be leveraged by remote attackers to execute arbitrary code using CVE-2016-3957.
The bug was discovered 04/05/2016. The weakness was shared 02/06/2018 (Website). The advisory is available at devco.re. This vulnerability is handled as CVE-2016-3954 since 04/05/2016. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 672 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.14.2 eliminates this vulnerability.
The entries VDB-112873 and VDB-112875 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: Web2py 2.14.2
Timeline
04/05/2016 🔍04/05/2016 🔍
02/06/2018 🔍
02/06/2018 🔍
02/07/2018 🔍
02/03/2023 🔍
Sources
Advisory: USN-4030-1Status: Not defined
CVE: CVE-2016-3954 (🔍)
GCVE (CVE): GCVE-0-2016-3954
GCVE (VulDB): GCVE-100-112874
See also: 🔍
Entry
Created: 02/07/2018 08:25Updated: 02/03/2023 16:07
Changes: 02/07/2018 08:25 (60), 01/02/2020 08:06 (1), 02/03/2023 16:07 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.