Skip to content
Fencer Vulns
medium 5.5

CVE-2006-1058 json

BusyBox 1.1.1 does not use a salt when generating passwords, which makes it easier for local users to guess passwords from a stolen passwor…

published 2006-04-04 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-1062

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits
0
none known

Summary

BusyBox 1.1.1 does not use a salt when generating passwords, which makes it easier for local users to guess passwords from a stolen password file using techniques such as rainbow tables.

Patch / fix

  • avaya aura_sip_enablement_services 5.0
  • avaya messaging_storage_server 4.0
  • busybox Debian 14, Debian 13, Debian 12 1:1.1.3-1

debian advisories DEBIAN-CVE-2006-1058

  • busybox RHEL 4 1.00.rc1-7.el4
  • busybox-anaconda RHEL 4 1.00.rc1-7.el4

red hat advisories RHSA-2007:0244

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-2006-1058 updated

security flaw

  • Red Hat Enterprise Linux AS version 4 busybox 1.00.rc1-7.el4, busybox-anaconda 1.00.rc1-7.el4 Red Hat Enterprise Linux Desktop version 4 busybox 1.00.rc1-7.el4, busybox-anaconda 1.00.rc1-7.el4 Red Hat Enterprise Linux ES version 4 busybox 1.00.rc1-7.el4, busybox-anaconda 1.00.rc1-7.el4 Red Hat Enterprise Linux WS version 4 busybox 1.00.rc1-7.el4, busybox-anaconda 1.00.rc1-7.el4
    fixed: vendor fix RHSA-2007:0244

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.29% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-916 Use of Password Hash With Insufficient Computational Effort

References

Sources

Fencer Vulns 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.