CVE-2020-8162

CVE-2020-8162 is a high-severity unrestricted upload of dangerous file types vulnerability in activestorage (rubygems), affecting versions >= 5.0.0, <= 5.2.4.2. It is fixed in 5.2.4.3, 6.0.3.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Circumvention of file size limits in ActiveStorage

There is a vulnerability in ActiveStorage's S3 adapter that allows the Content-Length of a direct file upload to be modified by an end user.

Versions Affected: rails < 5.2.4.2, rails < 6.0.3.1
Not affected: Applications that do not use the direct upload functionality of the ActiveStorage S3 adapter.
Fixed Versions: rails >= 5.2.4.3, rails >= 6.0.3.1

Impact

Utilizing this vulnerability, an attacker can control the Content-Length of an S3 direct upload URL without receiving a new signature from the server. This could be used to bypass controls in place on the server to limit upload size.

Workarounds

This is a low-severity security issue. As such, no workaround is necessarily until such time as the application can be upgraded.

Impact

The application accepts file uploads without adequately restricting the file type or content. Typical impact: remote code execution if the uploaded file can be served and executed on the server.

CVE-2020-8162 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.2.4.3, 6.0.3.1); upgrading removes the vulnerable code path.

Affected versions

activestorage (>= 5.0.0, <= 5.2.4.2) activestorage (>= 6.0.0, <= 6.0.3)

Security releases

activestorage → 5.2.4.3 (rubygems) activestorage → 6.0.3.1 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

activestorage to 5.2.4.3 or later; activestorage to 6.0.3.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2020-8162? CVE-2020-8162 is a high-severity unrestricted upload of dangerous file types vulnerability in activestorage (rubygems), affecting versions >= 5.0.0, <= 5.2.4.2. It is fixed in 5.2.4.3, 6.0.3.1. The application accepts file uploads without adequately restricting the file type or content.
  2. How severe is CVE-2020-8162? CVE-2020-8162 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of activestorage are affected by CVE-2020-8162? activestorage (rubygems) versions >= 5.0.0, <= 5.2.4.2 is affected.
  4. Is there a fix for CVE-2020-8162? Yes. CVE-2020-8162 is fixed in 5.2.4.3, 6.0.3.1. Upgrade to this version or later.
  5. Is CVE-2020-8162 exploitable, and should I be worried? Whether CVE-2020-8162 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2020-8162 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2020-8162?
    • Upgrade activestorage to 5.2.4.3 or later
    • Upgrade activestorage to 6.0.3.1 or later

Other vulnerabilities in activestorage

Stop the waste.
Protect your environment with Kodem.