oesa-2026-3477
Vulnerability from osv_openeuler
The DBI is the standard database interface module for Perl. It defines a set of methods, variables and conventions that provide a consistent database interface independent of the actual database being used. It is important to remember that the DBI is just an interface. The DBI is a layer of "glue" between an application and one or more database driver modules. It is the driver modules which do most of the real work. The DBI provides a standard interface and framework for the drivers to operate within.
Security Fix(es):
DBI versions before 1.652 for Perl allow a heap out-of-bounds write via an unvalidated numeric placeholder that sets the binder counter in preparse.
preparse reserves seven output bytes per input byte, the width of the longest ':p99999' expansion. The ':N' branch parses the number with atoi(src) and assigns it to the binder counter with no range check, so a statement containing ':2147483648' leaves the counter negative (-2147483648 with glibc, where atoi wraps). Each following '?' then expands through sprintf(start, ":p%d", idx++) to ':p-2147483648', 14 bytes with the terminating NUL where the buffer budgets 7. The placeholder limit added in 1.650 tests the counter against 99,999, which a negative counter passes.
Any caller that preparses an untrusted statement into ':pN' style placeholders gets a heap out-of-bounds write that grows with the number of '?' marks following the poisoned placeholder. The '?' and '%s' return styles compare the parsed number against the expected sequence and error out, and are unaffected.(CVE-2026-73194)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"perl-DBI-1.643-7.oe2403sp3.aarch64.rpm",
"perl-DBI-debuginfo-1.643-7.oe2403sp3.aarch64.rpm",
"perl-DBI-debugsource-1.643-7.oe2403sp3.aarch64.rpm"
],
"noarch": [
"perl-DBI-help-1.643-7.oe2403sp3.noarch.rpm"
],
"src": [
"perl-DBI-1.643-7.oe2403sp3.src.rpm"
],
"x86_64": [
"perl-DBI-1.643-7.oe2403sp3.x86_64.rpm",
"perl-DBI-debuginfo-1.643-7.oe2403sp3.x86_64.rpm",
"perl-DBI-debugsource-1.643-7.oe2403sp3.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP3",
"name": "perl-DBI",
"purl": "pkg:rpm/openEuler/perl-DBI\u0026distro=openEuler-24.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.643-7.oe2403sp3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The DBI is the standard database interface module for Perl. It defines a set of methods, variables and conventions that provide a consistent database interface independent of the actual database being used. It is important to remember that the DBI is just an interface. The DBI is a layer of \u0026amp;quot;glue\u0026amp;quot; between an application and one or more database driver modules. It is the driver modules which do most of the real work. The DBI provides a standard interface and framework for the drivers to operate within.\r\n\r\nSecurity Fix(es):\n\nDBI versions before 1.652 for Perl allow a heap out-of-bounds write via an unvalidated numeric placeholder that sets the binder counter in preparse.\n\npreparse reserves seven output bytes per input byte, the width of the longest \u0026apos;:p99999\u0026apos; expansion. The \u0026apos;:N\u0026apos; branch parses the number with `atoi(src)` and assigns it to the binder counter with no range check, so a statement containing \u0026apos;:2147483648\u0026apos; leaves the counter negative (-2147483648 with glibc, where atoi wraps). Each following \u0026apos;?\u0026apos; then expands through `sprintf(start, \u0026quot;:p%d\u0026quot;, idx++)` to \u0026apos;:p-2147483648\u0026apos;, 14 bytes with the terminating NUL where the buffer budgets 7. The placeholder limit added in 1.650 tests the counter against 99,999, which a negative counter passes.\n\nAny caller that preparses an untrusted statement into \u0026apos;:pN\u0026apos; style placeholders gets a heap out-of-bounds write that grows with the number of \u0026apos;?\u0026apos; marks following the poisoned placeholder. The \u0026apos;?\u0026apos; and \u0026apos;%s\u0026apos; return styles compare the parsed number against the expected sequence and error out, and are unaffected.(CVE-2026-73194)",
"id": "OESA-2026-3477",
"modified": "2026-08-20T10:01:03Z",
"published": "2026-08-20T10:01:03Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3477"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-73194"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "perl-DBI security update",
"upstream": [
"CVE-2026-73194"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.