CVE-2016-3954 web2py exposure of sensitive information
Remote attackers can obtain the session cookie key via a direct request, potentially leading to further exploitation.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2016-3954?
CVE-2016-3954 is a medium-severity vulnerability in n/a, published on 6 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Weakness: CWE-200
Which versions are affected by CVE-2016-3954?
3 open source packages ship an affected version, including web2py. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
web2py PyPI | All versions | 2.14.2 |
web2py PyPI | All versions | 2.14.2 |
web2py PyPI | All versions | 2.14.2 |
Products include Web2py Web2py.
How do I fix CVE-2016-3954?
Upgrade web2py to 2.14.2 or later.
Is CVE-2016-3954 being exploited?
There is no known exploitation of CVE-2016-3954 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2023-45158 Command injection in web2py
- CVE-2016-3953 web2py remote code execution via hardcoded encryption key in session.connect function
- CVE-2016-3957 Deserialization in n/a
- CVE-2016-10321 web2py is vulnerable to password brute-force attack
- CVE-2016-4808 Web2py Cross-Site Request Forgery vulnerability
Sources
Also known as GHSA-jr83-vr4j-mp6p, PYSEC-2026-1062, UBUNTU-CVE-2016-3954.