Article View: news.admin
Article #4064security holes in 2.11 news
From: dave
Date: Fri, 30 Jan 1987 18:16
Date: Fri, 30 Jan 1987 18:16
24 lines
1610 bytes
1610 bytes
It's no big secret that there are lots of holes on netnews.
For news administrators who are concerned about such things,
however, the spooling and batching mechanisms provide places
where someone could construct an article which appeared to
come from anyone, and leave it to get posted automatically.
1. If /usr/spool/news/.rnews (SPOOLDIR) is generally writeable,
anyone can leave an article there for processing.
2. If /usr/spool/news/batch (BATCHDIR) is writeable, or its individual
files are (i.e., system names), anyone can stick in a reference to
their own file or some file in /tmp (i.e., the file names waiting
to be batched don't have to be in /usr/spool/news), and that file
will get transferred as incoming news to the system in question.
Tightening up permissions on these directories should be possible,
but you have to at least make sure that sendbatch is run by news,
since sendbatch rm's the files in BATCHDIR. rnews is already setUID,
so should be able to handle a protected SPOOLDIR, I think.
David Sherman
The Law Society of Upper Canada
Toronto
--
{ seismo!mnetor cbosgd!utcs watmath decvax!utcsri ihnp4!utzoo } !lsuc!dave
Technical Details
Message-ID:
<1546@lsuc.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!lsuc!daveShow Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!lsuc!dave From: dave@lsuc.UUCP Newsgroups: news.admin Subject: security holes in 2.11 news Message-ID: <1546@lsuc.UUCP> Date: Fri, 30-Jan-87 13:16:31 EST Article-I.D.: lsuc.1546 Posted: Fri Jan 30 13:16:31 1987 Date-Received: Fri, 30-Jan-87 20:43:04 EST Sender: root@lsuc.UUCP Organization: Law Society of Upper Canada, Toronto Lines: 24