LiveActive security incident?Get immediate response
CVE Record

CVE-2014-3626: The Grails Resource Plugin often has to exchange URIs for resources with other internal components.

The Grails Resource Plugin often has to exchange URIs for resources with other internal components. Those other components will decode any URI passed to them. To protect against directory traversal the Grails Resource Plugin did the following: normalized the URI, checked the normalized URI did not step outside the appropriate root directory (e.g. the web application root), decoded the URI and checked that this did not introduce additional /../ (and similar) sequences. A bug was introduced where the Grails Resource Plugin before 1.2.13 returned the decoded version of the URI rather than the normalized version of the URI after the directory traversal check. This exposed a double decoding vulnerability. To address this issue, the Grails Resource Plugin now repeatedly decodes the URI up to three times or until decoding no longer changes the URI. If the decode limit of 3 is exceeded the URI is rejected. A side-effect of this is that the Grails Resource Plugin is unable to serve a resource that includes a '%' character in the full path to the resource. Not all environments are vulnerable because of the differences in URL resolving in different servlet containers. Applications deployed to Tomcat 8 and Jetty 9 were found not not be vulnerable, however applications deployed to JBoss EAP 6.3 / JBoss AS 7.4 and JBoss AS 7.1 were found to be vulnerable (other JBoss versions weren't tested). In certain cases JBoss returns JBoss specific vfs protocol urls from URL resolution methods (ClassLoader.getResources). The JBoss vfs URL protocol supports resolving any file on the filesystem. This made the directory traversal possible. There may be other containers, in addition to JBoss, on which this vulnerability is exposed.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
3

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.

description · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-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
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
2Source 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
Dell EMCGrails by PivotalResources plugin versions 1.2.0 - 1.2.12. Earlier versions may also be affected but were not assessedListed
Weakness

CWE details

No CWE listed

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