An issue was discovered in the DBI module through 1.643 for Perl.
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: perl-dbi (Alpine:v3.15) 1.643-r0; libdbi-perl (Debian:12) 1.643-3; libdbi-perl (Debian:9) 1.636-1+deb9u2.
Low priority for now. Upgrade to perl-dbi (Alpine:v3.15) 1.643-r0; libdbi-perl (Debian:12) 1.643-3; libdbi-perl (Debian:9) 1.636-1+deb9u2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered in the DBI module through 1.643 for Perl. DBD::File drivers can open files from folders other than those specifically passed via the f_dir attribute in the data source name (DSN). NOTE: this issue exists because of an incomplete fix for CVE-2014-10401.
- Published
- Sep 16, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 40th percentile
- CWE
- CWE-732
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| perl | dbi | cpe:2.3:a:perl:dbi |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- perl dbiup to 1.643 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.15 | perl-dbi | before 1.643-r0 | 1.643-r0 |
| Debian:12 | libdbi-perl | before 1.643-3 | 1.643-3 |
| Debian:9 | libdbi-perl | before 1.636-1+deb9u2 | 1.636-1+deb9u2 |
| openSUSE:Leap 15.1 | perl-DBI | before 1.639-lp151.3.16.1 | 1.639-lp151.3.16.1 |
| openSUSE:Leap 15.2 | perl-DBI | before 1.642-lp152.2.9.1 | 1.642-lp152.2.9.1 |
| openSUSE:Tumbleweed | perl-DBI | before 1.643-2.7 | 1.643-2.7 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP1 | perl-DBI | before 1.639-3.14.1 | 1.639-3.14.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP2 | perl-DBI | before 1.642-3.9.1 | 1.642-3.9.1 |
| SUSE:Linux Enterprise Server 12 SP5 | perl-DBI | before 1.628-5.9.1 | 1.628-5.9.1 |
Same product
perl: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-14739DBI versions before 1.650 for Perl have a heap overflow when preparsing SQL statements with an extreme number of placeholders39Monitor
- CVE-2026-9698DBI versions before 1.648 for Perl saved errors in a limited-sized buffer39Monitor
- CVE-2026-10879DBI versions before 1.648 for Perl have a heap overflow when preparsing SQL statements with more than 9 binders39Monitor
- CVE-2026-14740DBI versions before 1.650 for Perl read one byte out-of-bounds in preparse when deleting an initial SQL comment36Monitor
- CVE-2026-14380DBI versions before 1.650 for Perl are vulnerable to code injection via caller-influenced Profile35Monitor
- CVE-2014-10401An issue was discovered in the DBI module before 1.632 for Perl.24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:perl-dbi | 1.643-r0 · Alpine:v3.15 | Package registry (OSV) |
| debian:libdbi-perl | 1.643-3 · Debian:12 | Package registry (OSV) |
| opensuse:perl-DBI | 1.639-lp151.3.16.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| suse:perl-DBI | 1.642-3.9.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-732 · Incorrect Permission Assignment for Critical ResourceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Privilege AbuseCAPEC-122likelihood: High · Medium
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Exploiting Incorrectly Configured Access Control Security LevelsCAPEC-180likelihood: High · Medium
- Signing Malicious CodeCAPEC-206Very High
- Hijacking a privileged processCAPEC-234Medium
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
ATT&CK techniques
- File and Directory DiscoveryT1083
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Server Software Component: Terminal Services DLLT1505.005
- Abuse Elevation Control MechanismT1548
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Subvert Trust Controls:Code SigningT1553.002
- Compromise Client Software BinaryT1554
- Hijack Execution Flow:Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: ServicesFile Permissions WeaknessT1574.010
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.