Security readout for executives and security teams
Plain-English summary
This vulnerability affects older Grails Resource Plugin versions and can let a request escape the intended web resource directory in some servlet containers. In vulnerable JBoss deployments, the issue could expose files outside the application root. The available sources do not report active exploitation.
Executive priority
Treat confirmed vulnerable JBoss-hosted Grails applications as high priority because filesystem file exposure is possible. If the organization only used Tomcat 8 or Jetty 9, urgency is lower but version cleanup remains prudent.
Technical view
Grails Resource Plugin before 1.2.13 returned a decoded URI after traversal validation instead of the normalized URI. Components that decoded again could create double-decoding directory traversal. JBoss VFS URL handling was found vulnerable because it can resolve files across the filesystem; Tomcat 8 and Jetty 9 were reported not vulnerable.
Likely exposure
Exposure is likely limited to Grails applications using Resources plugin 1.2.0 through 1.2.12, possibly earlier unassessed versions, especially on JBoss EAP 6.3, JBoss AS 7.4, or JBoss AS 7.1.
Exploitation context
The source describes directory traversal through double-decoded resource URIs and JBoss VFS URL resolution. No KEV listing or cited source in the bundle confirms active exploitation or public exploit use.
Researcher notes
Evidence is strongest for Resources plugin 1.2.0-1.2.12 on listed JBoss versions. Earlier versions and other containers were not fully assessed in the source, so absence of evidence should not be treated as proof of safety.
Mitigation direction
- Upgrade Grails Resource Plugin to 1.2.13 or later.
- Prioritize JBoss EAP 6.3 and JBoss AS 7.x deployments.
- Check vendor guidance for unsupported or earlier unassessed plugin versions.
- Review whether servlet containers use URL resolution behavior similar to JBoss VFS.
Validation and detection
- Inventory Grails applications and Resources plugin versions.
- Map each application to its servlet container and version.
- Confirm no affected plugin version remains on vulnerable JBoss deployments.
- Review access logs for unusual resource traversal patterns without reproducing exploit behavior.
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.
File access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2014-3626 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://pivotal.io/security/cve-2014-3626CVE 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.
