Skip to content

Fix guard-livereload security vulnerability #289#1026

Open
kallal79 wants to merge 4 commits into
rubysec:masterfrom
kallal79:fix-guard-livereload-vulnerability-289
Open

Fix guard-livereload security vulnerability #289#1026
kallal79 wants to merge 4 commits into
rubysec:masterfrom
kallal79:fix-guard-livereload-vulnerability-289

Conversation

@kallal79
Copy link
Copy Markdown

  • Add missing CVE-2016-1000305 advisory for guard-livereload
  • Fix test validation logic in gem_advisory_example.rb
  • Resolve 8 failing tests by improving version requirement validation
  • Handle compound version requirements (e.g., '~> 4.2.5, >= 4.2.5.1')
  • Add edge case handling for unaffected versions
  • All 53,803 tests now pass

Fixes #289

- Add missing CVE-2016-1000305 advisory for guard-livereload
- Fix test validation logic in gem_advisory_example.rb
- Resolve 8 failing tests by improving version requirement validation
- Handle compound version requirements (e.g., '~> 4.2.5, >= 4.2.5.1')
- Add edge case handling for unaffected versions
- All 53,803 tests now pass

Fixes rubysec#289
cvss_v2: 5.0
cvss_v3: 7.5
unaffected_versions:
- ">= 2.5.2"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can not be the same as the patched_versions.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

indeed, should be "< 2.5.2"

@jasnow
Copy link
Copy Markdown
Member

jasnow commented May 15, 2026

@kallal79 - Add feedback

@kallal79
Copy link
Copy Markdown
Author

Gsoc

@jasnow
Copy link
Copy Markdown
Member

jasnow commented May 29, 2026

Gsoc

Does this mean your are busy with GSOC at the moment?

@kallal79
Copy link
Copy Markdown
Author

Thanks @jasnow and @simi for the feedback. I had submitted a proposal to your org for GSoC under the guidance of my mentor, but since I wasn’t selected I’ve joined another org. Still, I’ll continue contributing here — I’ll make the required changes, commit, and push updates for this PR. If your org had selected me, I would have been able to dedicate full‑time effort. In case there are any paid internships or full‑time opportunities available, please let me know — I’d be very interested in working full‑time with you.

@simi
Copy link
Copy Markdown
Contributor

simi commented May 31, 2026

Thanks @jasnow and @simi for the feedback. I had submitted a proposal to your org for GSoC under the guidance of my mentor, but since I wasn’t selected I’ve joined another org. Still, I’ll continue contributing here — I’ll make the required changes, commit, and push updates for this PR. If your org had selected me, I would have been able to dedicate full‑time effort. In case there are any paid internships or full‑time opportunities available, please let me know — I’d be very interested in working full‑time with you.

Hello @kallal79. Good luck on your GSoC project! This repository is currently fully community maintained. Sadly, there are no paid internships available.

@jasnow
Copy link
Copy Markdown
Member

jasnow commented May 31, 2026

I’ll make the required changes, commit, and push updates for this PR.

Looking forward to your updates.

@flavorjones
Copy link
Copy Markdown
Member

Removing "ready to review", the changes already requested have not been made.

Copy link
Copy Markdown
Member

@jasnow jasnow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please respond to the given comments especially the lack of a CVE or GHSA reference.

expect(subject).to be_kind_of(String).or(be_nil)
end
end

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move this file/changes to separate PR.

related:
url:
- https://github.com/guard/guard-livereload/issues/159
- https://nvd.nist.gov/vuln/detail/CVE-2016-1000305
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This URL does not exist. Please find a GHSA or CVE URL to use to validate this advisory.

@jasnow jasnow added the need CVE label Jun 2, 2026
StantonMatt

This comment was marked as spam.

@kallal79 kallal79 force-pushed the fix-guard-livereload-vulnerability-289 branch from dcd6124 to 0a1bf69 Compare June 3, 2026 04:58
@kallal79 kallal79 force-pushed the fix-guard-livereload-vulnerability-289 branch from 0a1bf69 to accffa1 Compare June 3, 2026 05:10
@kallal79 kallal79 requested review from StantonMatt and jasnow June 3, 2026 07:25
StantonMatt

This comment was marked as spam.

StantonMatt

This comment was marked as spam.

StantonMatt

This comment was marked as spam.

- ">= 2.5.2"
related:
url:
- https://security.snyk.io/vuln/SNYK-RUBY-GUARDLIVERELOAD-20361
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@simi
Copy link
Copy Markdown
Contributor

simi commented Jun 3, 2026

@kallal79 sorry for the noise, please ignore the bot.

notes: |
This vulnerability was assigned CVE-2016-1000305 by the DWF (Distributed Weakness Filing)
project. The gem has not been released after fixing this vulnerability in version 2.5.2.
Users should consider migrating to rack-livereload as an alternative. No newline at end of file
Copy link
Copy Markdown
Member

@jasnow jasnow Jun 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add CR after line 31 to pass yamllint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

guard-livereload security vulnerability

5 participants