Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

security vulnerability detected while using deploy to heroku #420

Open
roberthopman opened this issue Jul 27, 2018 · 4 comments
Open

security vulnerability detected while using deploy to heroku #420

roberthopman opened this issue Jul 27, 2018 · 4 comments

Comments

@roberthopman
Copy link

Expected outcome:
Deploy to Heroku works and I can start logging hours.

Actual outcome:


A security vulnerability has been detected in your application.
 !     To protect your application you must take action. Your application
 !     is currently exposing its credentials via an easy to exploit directory
 !     traversal.
 !     
 !     To protect your application you must either upgrade to Sprockets version "3.7.2"
 !     or disable dynamic compilation at runtime by setting:
 !     
 !     ```
 !     config.assets.compile = false # Disables security vulnerability
 !     ```
 !     
 !     To read more about this security vulnerability please refer to this blog post:
 !     https://blog.heroku.com/rails-asset-pipeline-vulnerability
 !
 !     Push rejected, failed to compile Ruby app.
 !     Push failed

@tarzan
Copy link
Member

tarzan commented Jul 27, 2018

You're right. We haven't done any maintenance or updates to application in quite a while. We know some dependencies have some security vulnerabilities in them. Feel free to fix them and open up a PR :)

@dnlamah
Copy link

dnlamah commented Aug 21, 2018

Hi, I am Daniel Amah. A Ruby on Rails developer. I will love to take on this task. @tarzan

1 similar comment
@DanielAmah
Copy link
Contributor

Hi, I am Daniel Amah. A Ruby on Rails developer. I will love to take on this task. @tarzan

@greysteil
Copy link

One fix for this would be #425

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants