2.1
CWE
264
Advisory Published
CVE Published
Updated

CVE-2014-3209

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 SoftwareAffected VersionHow 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

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2014-3209?

    CVE-2014-3209 is considered a medium severity vulnerability due to potential exposure of sensitive private keys.

  • How do I fix CVE-2014-3209?

    To remediate CVE-2014-3209, upgrade ldns to versions 1.7.1-2 or later.

  • What types of systems are affected by CVE-2014-3209?

    CVE-2014-3209 affects systems running ldns versions 1.6.x prior to 1.7.1.

  • What specific risk does CVE-2014-3209 pose?

    CVE-2014-3209 allows local users to read private key files due to inadequate permission settings based on current umask.

  • Is there a workaround for CVE-2014-3209 if I can't upgrade?

    A potential workaround for CVE-2014-3209 is to manually adjust the umask settings before generating private keys to limit access.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203