Closed
Bug 70573
Opened 25 years ago
Closed 24 years ago
".\n" in comments not escaped
Categories
(Bugzilla :: Creating/Changing Bugs, defect, P2)
Tracking
()
VERIFIED
DUPLICATE
of bug 117055
People
(Reporter: BenB, Assigned: myk)
References
Details
(Whiteboard: [escape])
If you write only a dot in the comment field, the bugmail contains no comment at
all. I wondered, why this is the case. A possible explanation is this bug.
The SMTP standard says that a dot on its own line ends the data of a msg. After
that, commands follow again. So, you might be able to place a dot and after that
SMTP command in a comment and make bugzilla issue them to the SMTP server.
Possible security bug.
Test:
.
SOME SMTP COMMAND HERE
MAIL FROM foo@example.com
RCPT TO ben.bucksch@beonex.com
DATA
hi
.
| Reporter | ||
Comment 1•25 years ago
|
||
The last line of the bugmail for the above was "Test:". I did not get any other
mail. So, doesn't seem to be a security bug.
Another test:
.
MAIL FROM bugzilla-daemon@mozilla.org
RCPT TO ben.bucksch@beonex.com
DATA
hi
.
Severity: critical → normal
Comment 2•25 years ago
|
||
Maybe the patch in bug 65101 fixes this?
Just a guess, but adding dependency. Please remove it if I'm wrong.
Depends on: 65101
Comment 3•25 years ago
|
||
Test...
.
RSET
MAIL FROM:<bugzilla-daemon@mozilla.org>
RCPT TO:<dave@intrec.com>
DATA
From: Dave <bugzilla-daemon@mozilla.org>
To: Dave <dave@intrec.com>
Subject: This is a test
This is a test.
Target Milestone: --- → Bugzilla 2.14
Comment 4•25 years ago
|
||
Hmm, we're using sendmail -t, and not SMTP for this, which is why the SMTP
commands aren't doing anything. sendmail -t exits when it gets a period on a
line by itself, which means the rest of it is just dumped. Removing 2.14
designation since this is definitely not a security issue. I agree that the
patch on bug 65101 would fix this. (It would also remove one more
incompatibility with Win32, too, which although I couldn't care less about
windows, is still a bonus. :)
Target Milestone: Bugzilla 2.14 → Bugzilla 2.16
| Reporter | ||
Comment 6•25 years ago
|
||
Jesse :-). even freaky bugs get dups :).
Updated•25 years ago
|
Priority: -- → P2
| Reporter | ||
Updated•25 years ago
|
Summary: ".\n" in coments not escaped → ".\n" in comments not escaped
Comment 7•24 years ago
|
||
-> Bugzilla product, Changing Bugs component, reassigning.
Assignee: tara → myk
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Whiteboard: [escape]
Version: Bugzilla 2.10 → 2.10
Comment 8•24 years ago
|
||
This ain't gonna be fixed outside of bug 65101.
Gerv
*** This bug has been marked as a duplicate of 65101 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Comment 9•24 years ago
|
||
clearing milestone for invalid/wontfix/worksforme/duplicate so they'll show up
as untriaged if they get reopened.
Target Milestone: Bugzilla 2.16 → ---
Comment 10•24 years ago
|
||
dupe of wrong bug...
Comment 11•24 years ago
|
||
117055 is newer, but had a patch, and actually got fixed.
*** This bug has been marked as a duplicate of 117055 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
Updated•13 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•