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: Timing Attack affecting rack-protection gem #1469

Merged
merged 1 commit into from
Aug 7, 2018

Conversation

mechanicles
Copy link
Contributor

  • Upgrade rack-protection gem version to fix timing attack
    vulnerability issue.
  • Currently, I have upgraded the version to "1.5.5" as this also fixes the same issue.

https://trello.com/c/CbleNB3C/712-qae18-security-timing-attack-affecting-rack-protection-gem

(https://trello.com/c/CbleNB3C/712-qae18-security-timing-attack-affecting-rack-protection-gem)

- Upgrade `rack-protection` gem version to fix timing attack
vulnerability issue.
@mechanicles
Copy link
Contributor Author

@matthewford @tomopey Security/snyk check got failed due to this XML External Entity (XXE) Injection issue in Nokogiri gem. I went through it, and I found that there is no proper solution until now. You can see this doc https://app.snyk.io/vuln/SNYK-RUBY-NOKOGIRI-20299, and it has this following info,

Nokogiri suggests not to opt-out of NONET unless only trusted documents are being parsed. There currently is no fix in libxml2 as of September 17th, 2017. Nokogiri will be waiting for a fix upstream to update.

You can also check this issue for the refer sparklemotion/nokogiri#1582

I feel that we should create a new card for this Nokogiri issue on the Trello. And let's merge this issue as this issue has nothing do with Nokogiri.

@matthewford matthewford merged commit a862c24 into master Aug 7, 2018
@matthewford matthewford deleted the 712-timing-attack branch August 7, 2018 18:16
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

Successfully merging this pull request may close these issues.

2 participants