Serendipity up to 2.0.4 SSRF Protection server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Serendipity up to 2.0.4. The impacted element is an unknown function of the component SSRF Protection. This manipulation with the input http://127.1 causes server-side request forgery.
This vulnerability is registered as CVE-2016-9752. Remote exploitation of the attack is possible. No exploit is available.
It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical was found in Serendipity up to 2.0.4 (Content Management System). Affected by this vulnerability is some unknown processing of the component SSRF Protection. The manipulation with the input value http://127.1 leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In Serendipity before 2.0.5, an attacker can bypass SSRF protection by using a malformed IP address (e.g., http://127.1) or a 30x (aka Redirection) HTTP status code.
The bug was discovered 12/02/2016. The weakness was published 12/01/2016 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2016-9752 since 12/01/2016. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
Upgrading to version 2.0.5 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 94622†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.6VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.6
VulDB Temp Score: 8.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.6
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: Server-side request forgeryCWE: CWE-918
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: Serendipity 2.0.5
Patch: github.com
Timeline
12/01/2016 🔍12/01/2016 🔍
12/01/2016 🔍
12/01/2016 🔍
12/01/2016 🔍
12/02/2016 🔍
10/04/2022 🔍
Sources
Advisory: fbdd50a448ed87ba34ea8c56446b8f1873eadd6f⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-9752 (🔍)
GCVE (CVE): GCVE-0-2016-9752
GCVE (VulDB): GCVE-100-93925
SecurityFocus: 94622 - Serendipity CVE-2016-9752 SSRF Security Bypass Vulnerability
Entry
Created: 12/01/2016 16:59Updated: 10/04/2022 17:59
Changes: 12/01/2016 16:59 (51), 06/14/2019 10:09 (13), 10/04/2022 17:59 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.