Lithium Forum 2017 Q1 Compose Message upload_url server-side request forgery

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.
4.8$0-$5k0.00

Summaryinfo

A vulnerability was found in Lithium Forum 2017 Q1. It has been rated as critical. This vulnerability affects unknown code of the component Compose Message Handler. The manipulation of the argument upload_url leads to server-side request forgery. This vulnerability is referenced as CVE-2017-20106. Furthermore, an exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Lithium Forum 2017 Q1 (Forum Software). This issue affects an unknown function of the component Compose Message Handler. The manipulation of the argument upload_url with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability.

The weakness was published 02/20/2017 by Vibhuti R V Nath as VL-ID 2030 as not defined advisory (Website). The advisory is shared at vulnerability-lab.com. The identification of this vulnerability is CVE-2017-20106. Technical details as well as a public exploit are known.

After immediately, there has been an exploit disclosed. The exploit is available at vulnerability-lab.com. It is declared as proof-of-concept.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 4.8

VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Server-side request forgery
CWE: CWE-918
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍

Timelineinfo

02/20/2017 🔍
02/20/2017 +0 days 🔍
02/24/2017 +4 days 🔍
06/25/2022 +1947 days 🔍

Sourcesinfo

Advisory: VL-ID 2030
Researcher: Vibhuti R V Nath
Status: Not defined

CVE: CVE-2017-20106 (🔍)
GCVE (CVE): GCVE-0-2017-20106
GCVE (VulDB): GCVE-100-97265
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 02/24/2017 15:59
Updated: 06/25/2022 18:21
Changes: 02/24/2017 15:59 (43), 08/17/2020 10:27 (2), 06/25/2022 18:21 (3)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!