- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 223
Add RubyGems's vulnerabilities fixed by 2.6.13. #298
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
          
     Closed
      
      
    
  
     Closed
                    Changes from all commits
      Commits
    
    
  File filter
Filter by extension
Conversations
          Failed to load comments.   
        
        
          
      Loading
        
  Jump to
        
          Jump to file
        
      
      
          Failed to load files.   
        
        
          
      Loading
        
  Diff view
Diff view
There are no files selected for viewing
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              | Original file line number | Diff line number | Diff line change | 
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| --- | ||
| library: rubygems | ||
| cve: 2017-0899 | ||
| url: http://blog.rubygems.org/2017/08/27/2.6.13-released.html | ||
| title: | | ||
| an ANSI escape sequence vulnerability. | ||
| date: 2017-08-27 | ||
| description: | | ||
| an ANSI escape sequence vulnerability. | ||
| patched_versions: | ||
| - ">= 2.6.13" | ||
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              | Original file line number | Diff line number | Diff line change | 
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| --- | ||
| library: rubygems | ||
| cve: 2017-0900 | ||
| url: http://blog.rubygems.org/2017/08/27/2.6.13-released.html | ||
| title: | | ||
| A DoS vulnerability in the query command. | ||
| date: 2017-08-27 | ||
| description: | | ||
| A DoS vulnerability in the query command. | ||
| patched_versions: | ||
| - ">= 2.6.13" | 
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              | Original file line number | Diff line number | Diff line change | 
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| --- | ||
| library: rubygems | ||
| cve: 2017-0901 | ||
| url: http://blog.rubygems.org/2017/08/27/2.6.13-released.html | ||
| title: | | ||
| A vulnerability in the gem installer that allowed a malicious gem to overwrite arbitrary files. | ||
| date: 2017-08-27 | ||
| description: | | ||
| A vulnerability in the gem installer that allowed a malicious gem to overwrite arbitrary files. | ||
| patched_versions: | ||
| - ">= 2.6.13" | 
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              | Original file line number | Diff line number | Diff line change | 
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| --- | ||
| library: rubygems | ||
| cve: 2017-0902 | ||
| url: http://blog.rubygems.org/2017/08/27/2.6.13-released.html | ||
| title: | | ||
| A DNS request hijacking vulnerability. | ||
| date: 2017-08-27 | ||
| description: | | ||
| A DNS request hijacking vulnerability. | ||
| patched_versions: | ||
| - ">= 2.6.13" | 
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's update the titles and descriptions for all of these to be aligned to the official CVE descriptions. These are not detailed enough based on our standards.
Use info from https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0899 for this one, as an example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@reedloden like this?
Or, description needs more information?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
titleanddescriptionare two different things. Title should be pretty short, while description is where most of the information will go. See https://github.com/rubysec/ruby-advisory-db#format for an example.For this one, perhaps "RubyGems Improper Neutralization of Escape Sequence" as title?
Also, please break the description on 80 chars and continue on next line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Title should be pretty short, and different from description is OK.
But I want to use announced sentence like
An ANSI escape sequence vulnerability., First sentence, ... This is because everyone can find easily.OK, I'll fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Chiming in a little late here, but you should simply use the title from the original advisory. Description is often the first paragraph or a brief summary of the advisory.