CVE-2013-4566: Medium severity red hat mod nss vulnerability

Published Oct 8, 2013
·
Updated

A flaw was found in the way NSSVerifyClient was handled when used in both server / vhost context as well as directory context (specified either via <Directory> or <Location> directive). If 'NSSVerifyClient none' was set in the server / vhost context (i.e. when server is configured to not request or require client certificate authentication on the initial connection), and client certificate authentication was expected to be required for a specific directory via 'NSSVerifyClient require' setting, modnss failed to properly require expected certificate authentication. Remote attacker able to connect to the web server using such modnss configuration and without a valid client certificate could possibly use this flaw to access content of the restricted directories.

Documentation of modnss configuration directives, including NSSVerifyClient:

https://git.fedorahosted.org/cgit/modnss.git/plain/docs/modnss.html#Directives

As modnss is derived form modssl, NSSVerifyClient is meant to be functionally equivalent to modssl's SSLVerifyClient:

http://httpd.apache.org/docs/2.2/mod/modssl.html#sslverifyclient

Other sources

modnss 1.0.8 and earlier, when NSSVerifyClient is set to none for the server/vhost context, does not enforce the NSSVerifyClient setting in the directory context, which allows remote attackers to bypass intended access restrictions.

MITRE

Affected Software

10 affected components
Mod Nss Project Mod Nss<=1.0.8
Mod Nss Project Mod Nss=1.0
Mod Nss Project Mod Nss=1.0.2
Mod Nss Project Mod Nss=1.0.3
Mod Nss Project Mod Nss=1.0.4
Mod Nss Project Mod Nss=1.0.5
Mod Nss Project Mod Nss=1.0.6
Mod Nss Project Mod Nss=1.0.7
redhat Enterprise Linux=5
redhat Enterprise Linux=6.0

Event History

Oct 8, 2013
Data Sourced
07:07 PM
DescriptionSeverityAffected Software
Dec 12, 2013
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2013-4566?

CVE-2013-4566 has a medium severity level due to its impact on client authentication.

2

How do I fix CVE-2013-4566?

To fix CVE-2013-4566, ensure that you do not set 'NSSVerifyClient none' in the server context and update to a patched version of mod_nss.

3

What versions are affected by CVE-2013-4566?

CVE-2013-4566 affects mod_nss versions up to 1.0.8 and specific versions like 1.0, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, and 1.0.7.

4

Is CVE-2013-4566 exploitable remotely?

Yes, CVE-2013-4566 is exploitable remotely, potentially allowing unauthorized access if not mitigated.

5

Who is impacted by CVE-2013-4566?

Organizations using affected versions of mod_nss in their server configurations are impacted by CVE-2013-4566.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203