Home / CVE DB / CVE-2015-3185
Standard
Vulnerability Identifier

CVE-2015-3185

2015-07-20
Severity Assessment
LOW
CVSS v3.x Score
Clinical Analysis (Description)

The ap_some_auth_required function in server/request.c in the Apache HTTP Server 2.4.x before 2.4.14 does not consider that a Require directive may be associated with an authorization setting rather than an authentication setting, which allows remote attackers to bypass intended access restrictions in opportunistic circumstances by leveraging the presence of a module that relies on the 2.2 API behavior.

Vector Sequencing

Attack Parameters

Impact Consequences

Technical Impact

CVSS v2 Score (Legacy)
4.3

For backward compatibility

EPSS Probability
9.49%

Percentile: 92.9%

Weakness Classification

CWE-CWE-264

Affected Population

Affected Configurations

Total: 18 detected entries

Software List Scrollable
ap
http_server
Vendor: apache • v2.4.13
ca
ubuntu_linux
Vendor: canonical • v14.04
ap
mac_os_x
Vendor: apple • v10.10.4
ap
http_server
Vendor: apache • v2.4.4
ap
http_server
Vendor: apache • v2.4.8
ap
http_server
Vendor: apache • v2.4.12
ap
http_server
Vendor: apache • v2.4.9
ap
mac_os_x_server
Vendor: apple • v5.0.3
ap
xcode
Vendor: apple • v7.0
ap
http_server
Vendor: apache • v2.4.0
ca
ubuntu_linux
Vendor: canonical • v12.04
ap
http_server
Vendor: apache • v2.4.10
ap
http_server
Vendor: apache • v2.4.7
ca
ubuntu_linux
Vendor: canonical • v15.04
ap
http_server
Vendor: apache • v2.4.2
ap
http_server
Vendor: apache • v2.4.6
ap
http_server
Vendor: apache • v2.4.1
ap
http_server
Vendor: apache • v2.4.3
Timeline

Time Line

PUBLICATION
20 Jul 2015
MODIFICATION
12 Apr 2025
Impact Statistics

Key Metrics

CVSS Score
LOW
Products
18
Affected
Remediation Protocol

Recommended Solution

No automatic solution found. Check vendor references.
Patch Library
No direct patch listed in database.
Recommended Actions for Administrators

Immediate Action Plan

1. Inventory

Identify all affected systems in your infrastructure.

2. Assessment

Assess exposure and criticality for your organization.

3. Mitigation

Apply patches or available workarounds.

4. Verification

Test and confirm effectiveness of applied measures.