CVE-2006-1058: Medium severity Busybox Busybox vulnerability
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2006-1058?
CVE-2006-1058 is considered a high severity vulnerability due to the lack of password salting, making it easier for attackers to exploit stolen password files.
How do I fix CVE-2006-1058?
To fix CVE-2006-1058, upgrade to a version of BusyBox that includes salt in password generation or implement an external solution that mitigates password cracking.
Who is affected by CVE-2006-1058?
CVE-2006-1058 affects systems running BusyBox version 1.1.1 and certain Avaya products that utilize BusyBox for password management.
What are the risks associated with CVE-2006-1058?
The risks associated with CVE-2006-1058 include unauthorized access to systems and data as attackers can easily crack unsalted passwords.
How can I mitigate the impact of CVE-2006-1058?
To mitigate the impact of CVE-2006-1058, consider using stronger password policies, multi-factor authentication, and regularly auditing password strength.