Skip to content
Fencer Intel
low 1.9

CVE-2010-0826 json

The Free Software Foundation (FSF) Berkeley DB NSS module (aka libnss-db) 2.2.3pre1 reads the DB_CONFIG file in the current working directo…

published 16y ago modified 4mo ago also EUVD-2010-0852

cvss
1.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

The Free Software Foundation (FSF) Berkeley DB NSS module (aka libnss-db) 2.2.3pre1 reads the DB_CONFIG file in the current working directory, which allows local users to obtain sensitive information via a symlink attack involving a setgid or setuid application that uses this module.

Patch / fix

  • libnss-db Debian 13, Debian 12 2.2.3pre1-3.2

debian advisories DEBIAN-CVE-2010-0826

  • nss_db RHEL 5 2.2-35.4.el5_5

red hat advisories RHSA-2010:0347

Is CVE-2010-0826 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-0826 updated cvss 1.9

nss_db: Information leak due the DB_CONFIG file read from current working directory

  • Red Hat Enterprise Linux (v. 5 server) nss_db 2.2-35.4.el5_5 Red Hat Enterprise Linux Desktop (v. 5 client) nss_db 2.2-35.4.el5_5
    fixed: vendor fix RHSA-2010:0347

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.