First published: Sat May 03 2014(Updated: )
The ldns-keygen tool in ldns 1.6.x uses the current umask to set the privileges of the private key, which might allow local users to obtain the private key by reading the file.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/ldns | 1.7.1-2 1.8.3-1 1.8.4-1 | |
NLnet Labs LDNS | =1.6.0 | |
NLnet Labs LDNS | =1.6.1 | |
NLnet Labs LDNS | =1.6.2 | |
NLnet Labs LDNS | =1.6.3 | |
NLnet Labs LDNS | =1.6.4 | |
NLnet Labs LDNS | =1.6.5 | |
NLnet Labs LDNS | =1.6.6 | |
NLnet Labs LDNS | =1.6.7 | |
NLnet Labs LDNS | =1.6.8 | |
NLnet Labs LDNS | =1.6.9 | |
NLnet Labs LDNS | =1.6.10 | |
NLnet Labs LDNS | =1.6.11 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-3209 is considered a medium severity vulnerability due to potential exposure of sensitive private keys.
To remediate CVE-2014-3209, upgrade ldns to versions 1.7.1-2 or later.
CVE-2014-3209 affects systems running ldns versions 1.6.x prior to 1.7.1.
CVE-2014-3209 allows local users to read private key files due to inadequate permission settings based on current umask.
A potential workaround for CVE-2014-3209 is to manually adjust the umask settings before generating private keys to limit access.