Security readout for executives and security teams
Plain-English summary
This affects Ruby applications using the i18n gem before 0.8.0. A specific Hash#slice edge case can crash the application, causing denial of service. Business risk depends on whether untrusted input can reach the vulnerable call pattern. Sources do not show data theft, code execution, or confirmed active exploitation.
Executive priority
Treat this as a legacy dependency denial-of-service issue. It is not evidenced as actively exploited, but internet-facing or business-critical Ruby services using old i18n versions should be remediated during normal vulnerability maintenance.
Technical view
Hash#slice in lib/i18n/core_ext/hash.rb mishandled a keep_keys entry that was requested but absent from the hash, leading to an application crash. The issue is documented as fixed before i18n 0.8.0, with a Debian ruby-i18n security update also referenced. Validation should focus on installed gem versions and reachable application paths.
Likely exposure
Exposure is most likely in legacy Ruby applications or systems packaging ruby-i18n with versions before 0.8.0. The provided sources do not identify specific applications beyond the i18n gem and Debian ruby-i18n package context.
Exploitation context
The CVE description says remote attackers may trigger denial of service in a specific call situation. The source bundle does not include KEV listing, public exploit confirmation, or evidence of active exploitation in the wild.
Researcher notes
The bundle lacks CVSS, CWE, and detailed exploit prerequisites. Analysis should avoid assuming broad reachability. The important technical question is whether application-controlled data can cause Hash#slice to request keys absent from the target hash.
Mitigation direction
- Upgrade the i18n gem to version 0.8.0 or later where compatible.
- Apply vendor package updates for ruby-i18n on supported operating systems.
- Check vendor guidance before backporting fixes to unsupported legacy versions.
- Prioritize exposed services where user input may influence i18n hash handling.
Validation and detection
- Inventory Ruby applications and packages for i18n versions before 0.8.0.
- Review lockfiles, package manifests, and deployed gem versions for ruby-i18n.
- Confirm whether vulnerable code paths are reachable from remote requests.
- Check logs for unexplained application crashes around translation or parameter handling.
Public sources used
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.
CVE-2014-10077 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/svenfuchs/i18n/releases/tag/v0.8.0CVE reference · x_refsource_MISC
- https://github.com/rubysec/ruby-advisory-db/pull/182/filesCVE reference · x_refsource_MISC
- [debian-lts-announce] 20181121 [SECURITY] [DLA 1584-1] ruby-i18n security updateCVE reference · mailing-list, x_refsource_MLIST
- https://github.com/svenfuchs/i18n/pull/289CVE reference · x_refsource_MISC
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.
