Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2014-0053: The default configuration of the Resources plugin 1.0.0 before 1.2.6 for Pivotal Grails 2.0.0 before 2.3.6 doe

38
Routine
MEDIUM 5.0DOWNGRADEDOWNGRADE

CVE-2014-0053 is a medium-severity flaw (CVSS 5.0) affecting grails-resources, grails. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The default configuration of the Resources plugin 1.0.0 before 1.2.6 for Pivotal Grails 2.0.0 before 2.3.6 does not properly restrict access to files in the WEB-INF directory, which allows remote attackers to obtain sensitive information via a direct request. NOTE: this identifier has been SPLIT due to different researchers and different vulnerability types. See CVE-2014-2857 for the META-INF variant and CVE-2014-2858 for the directory traversal

Why this priority

  • No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score5.0 (Medium)
EPSS exploit chance2.0% (top 19%)
CISA exploited listNo
WeaknessCWE-264
Published2014-04-15
Last modified2026-06-17
Publisher (CNA): Red Hat, Inc. · Vendor: gopivotal

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

gopivotal grails-resources DOWNGRADE
Affected: 1.0.0 · 1.0.2 · 1.1.0 · 1.1.1 · 1.1.2 · 1.1.4 · 1.1.5 · 1.1.6
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0.0
1. Check installed version
apt-cache policy grails-resources || rpm -q grails-resources || grails-resources --version
2. No fixed release: DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)
apt-cache madison grails-resources sudo apt install grails-resources=<VERSION_BEFORE_1.0.0> sudo apt-mark hold grails-resources
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list grails-resources sudo dnf downgrade grails-resources-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add grails-resources
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
gopivotal grails DOWNGRADE
Affected: 2.0.0 · 2.0.1 · 2.0.2 · 2.0.3 · 2.0.4 · 2.1.0 · 2.1.1 · 2.1.2
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy grails || rpm -q grails || grails --version
2. No fixed release: DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)
apt-cache madison grails sudo apt install grails=<VERSION_BEFORE_2.0.0> sudo apt-mark hold grails
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list grails sudo dnf downgrade grails-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add grails
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2014-0053?

grails-resources: downgrade or apply the listed mitigation; grails: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2014-0053 being exploited?

CVE-2014-0053 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2014-0053 affect?

CVE-2014-0053 affects grails-resources, grails. Severity is medium (CVSS 5.0). The default configuration of the Resources plugin 1.0.0 before 1.2.6 for Pivotal Grails 2.0.0 before 2.3.6 does not properly restrict access to files in the WEB-INF directory, which allows remote attackers to obtain sensitive information vi

How urgent is CVE-2014-0053?

Priority 38/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.