CVE-2017-0373

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.

Published: 2017-05-23 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-0373 is rated Moderate Risk (57.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.84%). EPSS rose +1.35% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-0373

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.49% 1.84% +1.35%
2 2025-03-17 0.15% 0.49% +0.34%
3 2023-05-03 — 0.15% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-0373

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.3 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.3 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2017-0373

OS Trackers for CVE-2017-0373

vendor priority summary link
debian not yet assigned CVE-2017-0373 not yet assigned priority: Debian including 1 source packages (libconfig-model-perl), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-0373
ubuntu medium CVE-2017-0373 medium priority: Ubuntu including 1 source packages (libconfig-model-perl), 22 status rows across 22 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial, yakkety, zesty): not-affected 17, ignored 2, DNE 1, needed 1, released 1. https://ubuntu.com/security/CVE-2017-0373

Affected software / configurations for CVE-2017-0373

Vendor Product Version Raw CPE
config-model_project config-model <= 2.101 cpe:2.3:a:config-model_project:config-model:*:*:*:*:*:*:*:*

References for CVE-2017-0373

cvelogic Threat Intelligence