flitto express-param up to 0.x lib/fetchParams.js parameter pollution

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.
7.4$0-$5k0.67

Summaryinfo

A vulnerability identified as problematic has been detected in flitto express-param up to 0.x. This impacts an unknown function of the file lib/fetchParams.js. Performing a manipulation results in parameter pollution. This vulnerability is cataloged as CVE-2017-20160. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in flitto express-param up to 0.x. It has been classified as critical. This affects some unknown functionality of the file lib/fetchParams.js. The manipulation with an unknown input leads to a parameter pollution vulnerability. CWE is classifying the issue as CWE-235. The product does not handle or incorrectly handles when the number of parameters, fields, or arguments with the same name exceeds the expected amount. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was shared 12/31/2022 as 19. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2017-20160. Technical details are known, but no exploit is available.

Upgrading to version 1.0.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch db94f7391ad0a16dcfcba8b9be1af385b25c42db 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.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB 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): 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Parameter pollution
CWE: CWE-235 / CWE-233 / CWE-229
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: express-param 1.0.0
Patch: db94f7391ad0a16dcfcba8b9be1af385b25c42db

Timelineinfo

12/31/2022 🔍
12/31/2022 +0 days 🔍
12/31/2022 +0 days 🔍
01/26/2023 +26 days 🔍

Sourcesinfo

Product: github.com

Advisory: 19
Status: Confirmed

CVE: CVE-2017-20160 (🔍)
GCVE (CVE): GCVE-0-2017-20160
GCVE (VulDB): GCVE-100-217149

Entryinfo

Created: 12/31/2022 20:20
Updated: 01/26/2023 15:08
Changes: 12/31/2022 20:20 (43), 01/26/2023 15:04 (2), 01/26/2023 15:08 (28)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!