/ 
DBI-1.654
⭐ Starred 84 / dbiprof
Security Advisories (2)
CVE-2026-108518 (2026-10-20)

DBI versions before 1.656 for Perl crash via type confusion in dbi_profile when a database handle is destroyed under a Profile Path with an {attr} element. An {attr} element names a database handle attribute, which dbi_profile reads from the handle's inner hash. It expects the inner handle as a reference and dereferences it, but a handle that is being destroyed hands back the inner hash itself, so the dereference yields the hash's bucket array. A type check on that pointer usually fails and the call goes unprofiled. When the memory it addresses passes the check, the attribute lookup dereferences a NULL or invalid pointer and the process dies on SIGSEGV. The Path is set by the application, by the Profile handle attribute, or by the DBI_PROFILE environment variable, so `DBI_PROFILE={ImplementorClass}` can crash an unmodified program.

CVE-2026-111879 (2026-10-20)

DBI versions before 1.656 for Perl hang on a later open of a DBD::DBM table because a failed open_data does not release the table's lock. open_data creates the table's lock file and takes an exclusive flock on it for a CREATE, before the checks that can croak: a dbm_mldbm value that is not a module name, a failing tie, or a missing data file. The croak unwinds before the table object is blessed, so nothing releases the lock, and the meta data holding the open descriptor stays cached on the database handle. The dbm_mldbm and dbm_type values come from the DSN or the connect attributes, so a caller that chooses the serializer or the storage backend can trigger the failure. The flock has no timeout, so a later open of that table (even through a separate database handle) blocks for as long as the handle holding the stale lock lives, in the same process or any other.

NAME

dbiprof - command-line client for DBI::ProfileData

SYNOPSIS

See a report of the ten queries with the longest total runtime in the profile dump file prof1.out:

dbiprof prof1.out

See the top 10 most frequently run queries in the profile file dbi.prof (the default):

dbiprof --sort count

See the same report with 15 entries:

dbiprof --sort count --number 15

DESCRIPTION

This tool is a command-line client for the DBI::ProfileData. It allows you to analyze the profile data file produced by DBI::ProfileDumper and produce various useful reports.

OPTIONS

This program accepts the following options:

--number N

Produce this many items in the report. Defaults to 10. If set to "all" then all results are shown.

--sort field

Sort results by the given field. Sorting by multiple fields isn't currently supported (patches welcome). The available sort fields are:

total

Sorts by total time run time across all runs. This is the default sort.

longest

Sorts by the longest single run.

count

Sorts by total number of runs.

first

Sorts by the time taken in the first run.

shortest

Sorts by the shortest single run.

key1

Sorts by the value of the first element in the Path, which should be numeric. You can also sort by key2 and key3.

--reverse

Reverses the selected sort. For example, to see a report of the shortest overall time:

dbiprof --sort total --reverse
--match keyN=value

Consider only items where the specified key matches the given value. Keys are numbered from 1. For example, let's say you used a DBI::Profile Path of:

[ DBIprofile_Statement, DBIprofile_Methodname ]

And called dbiprof as in:

dbiprof --match key2=execute

Your report would only show execute queries, leaving out prepares, fetches, etc.

If the value given starts and ends with slashes (/) then it will be treated as a regular expression. For example, to only include SELECT queries where key1 is the statement:

dbiprof --match key1=/^SELECT/

By default the match expression is matched case-insensitively, but this can be changed with the --case-sensitive option.

--exclude keyN=value

Remove items for where the specified key matches the given value. For example, to exclude all prepare entries where key2 is the method name:

dbiprof --exclude key2=prepare

Like --match, If the value given starts and ends with slashes (/) then it will be treated as a regular expression. For example, to exclude UPDATE queries where key1 is the statement:

dbiprof --match key1=/^UPDATE/

By default the exclude expression is matched case-insensitively, but this can be changed with the --case-sensitive option.

--case-sensitive

Using this option causes --match and --exclude to work case-sensitively. Defaults to off.

--delete

Sets the DeleteFiles option to DBI::ProfileData which causes the files to be deleted after reading. See DBI::ProfileData for more details.

--dumpnodes

Print the list of nodes in the form of a perl data structure. Use the -sort option if you want the list sorted.

--version

Print the dbiprof version number and exit.

AUTHOR

Sam Tregar <sam@tregar.com>

COPYRIGHT AND LICENSE

Copyright (C) 2002 Sam Tregar

This program is free software; you can redistribute it and/or modify it under the same terms as Perl 5 itself.

SEE ALSO

DBI::ProfileDumper, DBI::Profile, DBI.