Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

redhat логотип

CVE-2026-73194

Опубликовано: 15 авг. 2026
Источник: redhat
CVSS3: 7.3
EPSS Низкий

Описание

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.

A flaw was found in DBI for Perl. An unvalidated numeric placeholder in the preparse function can lead to a heap out-of-bounds write. When processing an untrusted statement, a specially crafted numeric placeholder can cause the binder counter to become negative. This results in subsequent placeholders expanding beyond their allocated buffer, leading to memory corruption. An attacker could exploit this to potentially achieve arbitrary code execution or cause a denial of service.

Отчет

This vulnerability is classified with an Important severity because heap memory corruption can be triggered to compromise process execution flow or crash the service. In typical Red Hat Enterprise Linux deployments, database interactions rely on fixed query templates and bound values rather than permitting external users to supply raw queries to the parser. Consequently, exposure is limited to specific architectures or custom scripts that directly parse untrusted query strings using numbered binder substitutions.

Меры по смягчению последствий

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Затронутые пакеты

ПлатформаПакетСостояниеРекомендацияРелиз
Red Hat Enterprise Linux 6perl-DBIOut of support scope
Red Hat Enterprise Linux 7perl-DBIAffected
Red Hat Enterprise Linux 10perl-DBIFixedRHSA-2026:7075323.09.2026
Red Hat Enterprise Linux 8perl-DBIFixedRHSA-2026:6911221.09.2026
Red Hat Enterprise Linux 8perl-DBIFixedRHSA-2026:7160824.09.2026
Red Hat Enterprise Linux 9perl-DBIFixedRHSA-2026:7142224.09.2026

Показывать по

Дополнительная информация

Статус:

Important
Дефект:
CWE-787
https://bugzilla.redhat.com/show_bug.cgi?id=2516959perl-DBI: DBI for Perl: Heap out-of-bounds write via unvalidated numeric placeholder

EPSS

Процентиль: 43%
0.00493
Низкий

7.3 High

CVSS3

Связанные уязвимости

CVSS3: 9.1
ubuntu
3 месяца назад

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 seque...

CVSS3: 9.1
nvd
3 месяца назад

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 sequen

msrc
3 месяца назад

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

CVSS3: 9.1
debian
3 месяца назад

DBI versions before 1.652 for Perl allow a heap out-of-bounds write vi ...

CVSS3: 9.1
redos
около 2 месяцев назад

Уязвимость perl-DBI

EPSS

Процентиль: 43%
0.00493
Низкий

7.3 High

CVSS3