LiveActive security incident?Get immediate response
CVE Record

CVE-2014-8109: mod_lua.c in the mod_lua module in the Apache HTTP Server 2.3.x and 2.4.x through 2.4.10 does not support a...

mod_lua.c in the mod_lua module in the Apache HTTP Server 2.3.x and 2.4.x through 2.4.10 does not support an httpd configuration in which the same Lua authorization provider is used with different arguments within different contexts, which allows remote attackers to bypass intended access restrictions in opportunistic circumstances by leveraging multiple Require directives, as demonstrated by a configuration that specifies authorization for one group to access a certain directory, and authorization for a second group to access a second directory.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This Apache HTTP Server issue affects mod_lua authorization logic. In specific configurations, access rules using the same Lua authorization provider with different arguments in different locations can be mixed up, allowing a remote user to bypass intended access restrictions. The supplied sources describe unauthorized access risk, not code execution. Exposure is limited to Apache HTTP Server deployments using mod_lua LuaAuthzProvider with the same provider name and different arguments in different authorization contexts. Generic Apache installations without mod_lua authorization providers are not shown as affected in the supplied sources. Treat as a targeted access-control risk for older Apache environments, especially internet-facing sites with custom Lua authorization. Prioritize validation where protected web content, customer portals, admin paths, or regulated data depend on Apache authorization rules. Mitigation focus: Identify Apache servers using mod_lua and LuaAuthzProvider authorization rules.; Apply vendor Apache HTTP Server updates containing the referenced mod_lua fix.; Review configurations reusing the same Lua authorization provider with different arguments..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2014-8109 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
18Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.