Security readout for executives and security teams
Plain-English summary
liblouis 2.5.x before 2.5.4 contains a stack buffer overflow. If a user opens a malicious file in software that uses liblouis, such as Orca, the application may crash or potentially run attacker-controlled code.
Executive priority
Treat as high priority where affected liblouis versions are present in user-facing workflows. The business risk is user-assisted code execution or service disruption, not a proven internet-wide exploitation campaign.
Technical view
CVE-2014-8184 is a CWE-121 stack-based buffer overflow in findTable() in liblouis. The CVSS 3.0 score is 7.8 with local attack vector, low complexity, no privileges required, and required user interaction.
Likely exposure
Exposure is most likely on systems running liblouis 2.5.x before 2.5.4, especially assistive technology or document-processing workflows that open files through liblouis-dependent applications.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The described scenario requires a malicious file to be opened by a user in an affected liblouis-consuming application.
Researcher notes
Focus validation on liblouis 2.5.x before 2.5.4 and downstream packages. The source bundle names findTable() and crash or potential arbitrary code execution, but does not provide exploit confirmation or detailed vendor remediation beyond the fixed version boundary.
Mitigation direction
- Upgrade liblouis to 2.5.4 or a vendor-supported fixed package.
- Check Red Hat or distribution advisories for backported fixes.
- Reduce handling of untrusted files in affected liblouis-consuming applications.
- Prioritize systems supporting accessibility workflows or automated document processing.
Validation and detection
- Inventory installed liblouis versions across endpoints and server images.
- Identify applications that link to or package liblouis.
- Confirm package changelogs or vendor metadata reference the CVE fix.
- Review whether users receive or open untrusted files in affected workflows.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2014-8184 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
7.8HighVector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/liblouis/liblouis/issues/425CVE reference · x_refsource_MISC
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-8184CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.