Hi all,
While reviewing a bug, a question arises: shouldn't repeated newsgroups
in Xref header fields be considered as an error, and the article be
rejected during both injection and relaying?
Though repeats could also happen in other header fields like Newsgroups,
this seems harmless; de-duplication will be done by the server or client
when processing the header field. However, as for Xref, we expect the
peer to have de-duplicated already, so repeats should not happen here,
and are almost certainly an attack signature.
Any thoughts about that? Has someone recently seen valid articles with duplicated Xref header fields?
Digging into Jesse's archives could be interesting :-)
While reviewing a bug, a question arises: shouldn't repeated newsgroups
in Xref header fields be considered as an error, and the article be
rejected during both injection and relaying?
Injecting agents MUST reject an article with Xref.
With that, in my opinion, a transit server isn't required to strip or examine Xref.
In the case of duplicate newsgroups in the same Xref header... I am not seeing
anything that says the newsgroups have to be unique inside the header, but also don't see how an article can have more than one article number per newsgroup.
Hi Jesse,
While reviewing a bug, a question arises: shouldn't repeated newsgroups
in Xref header fields be considered as an error, and the article be
rejected during both injection and relaying?
Injecting agents MUST reject an article with Xref.
Indeed. My question was wrong; I shouldn't have spoken about roles, but
only about syntax checks.
With that, in my opinion, a transit server isn't required to strip or examine
Xref.
Yes, unless these transit servers also store articles or history. The
use case is to have access to these articles to relay them to peers (and eventually delete them as soon as all the remote peers have accepted or rejected the articles sent).
Programs like archive, expire, overchan or makehistory parse that field.
When innd acts as a slave server, it also examines the Xref header field.
In the case of duplicate newsgroups in the same Xref header... I am not seeing
anything that says the newsgroups have to be unique inside the header, but >> also don't see how an article can have more than one article number per
newsgroup.
That's the point of my message. There shouldn't be such repeated
newsgroups in the Xref header field. It could be a form of attack to
trigger bugs. It is what we are currently examining with Billy G and
Richard Kettlewell, thus the suggestion to harden a bit the allowed
syntax of that header field.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 56:09:34 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,718 |