forked from rubysec/ruby-advisory-db
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixes rubysec#215.
- Loading branch information
Showing
1 changed file
with
24 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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,24 @@ | ||
--- | ||
gem: mail | ||
osvdb: 131677 | ||
url: http://www.mbsd.jp/Whitepaper/smtpi.pdf | ||
title: Mail Gem for Ruby SMTP Injection via recipient email addresses | ||
date: 2015-12-09 | ||
|
||
description: | | ||
Mail Gem for Ruby is vulnerable to the recipient attack described in Takeshi | ||
Terada's "SMTP Injection via recipient email addresses" whitepaper | ||
(http://www.mbsd.jp/Whitepaper/smtpi.pdf), as it does not validate nor | ||
sanitize given recipient addresses. Thus, the attacks described in the paper | ||
can be applied to the library without any modification. | ||
[email protected]>[CRLF]DATA[CRLF](message content)[CRLF].[CRLF]QUIT[CRLF] | ||
The Mail library itself does not impose a length limit on email addresses, | ||
so an attacker can send a long spam message via a recipient address unless | ||
there is a limit on the application's side. | ||
This vulnerability affects only applications that lack input validation. | ||
patched_versions: | ||
- ">= 2.6.0" |