Config-Model up to 2.x Debian Package FIle GenClassPod.pm input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Config-Model up to 2.x. This affects an unknown function in the library lib/Config/Model/Utils/GenClassPod.pm of the component Debian Package FIle Handler. This manipulation causes input validation. This vulnerability is registered as CVE-2017-0373. The attack needs to be launched locally. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Config-Model up to 2.x. It has been declared as critical. Affected by this vulnerability is an unknown functionality in the library lib/Config/Model/Utils/GenClassPod.pm of the component Debian Package FIle Handler. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The gen_class_pod implementation in lib/Config/Model/Utils/GenClassPod.pm in Config-Model (aka libconfig-model-perl) before 2.102 has a dangerous "use lib" line, which allows remote attackers to have an unspecified impact via a crafted Debian package file.
The bug was discovered 05/14/2017. The weakness was published 05/23/2017 (Website). The advisory is shared at cpansearch.perl.org. This vulnerability is known as CVE-2017-0373 since 11/29/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 9 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.102 eliminates this vulnerability.
Similar entry is available at VDB-101726. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.3
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: Input validationCWE: CWE-20
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: Config-Model 2.102
Patch: anonscm.debian.org
Timeline
11/29/2016 🔍05/14/2017 🔍
05/23/2017 🔍
05/23/2017 🔍
05/24/2017 🔍
12/07/2022 🔍
Sources
Advisory: cpansearch.perl.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2017-0373 (🔍)
GCVE (CVE): GCVE-0-2017-0373
GCVE (VulDB): GCVE-100-101725
OSVDB: - CVE-2017-0373 - Config-Model - Unspecified Issue
See also: 🔍
Entry
Created: 05/24/2017 08:41Updated: 12/07/2022 09:29
Changes: 05/24/2017 08:41 (59), 10/02/2020 16:46 (3), 12/07/2022 09:29 (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.