mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guest section DW <dwguest@win.tue.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, kernel@ddx.a2000.nu
Cc: linux-kernel@vger.kernel.org, enforcer@ddx.a2000.nu (Enforcer)
Subject: Re: Strange errors in /var/log/messages
Date: Mon, 2 Jul 2001 19:42:12 +0200	[thread overview]
Message-ID: <20010702194212.A400@win.tue.nl> (raw)
In-Reply-To: <Pine.LNX.4.30.0107021800410.5490-100000@ddx.a2000.nu> <E15H6N5-000663-00@the-village.bc.nu>
In-Reply-To: <E15H6N5-000663-00@the-village.bc.nu>; from Alan Cox on Mon, Jul 02, 2001 at 05:16:23PM +0100

On Mon, Jul 02, 2001 at 05:16:23PM +0100, Alan Cox wrote:

> > I'm running RedHat 7.0 with all official RH patches applied. The kernel I
> > currently run fow a few days is 2.2.19-7.0.8
> > I run the pre-compiled kernel of RH. Suddenly I the following messages:
> > 
> > Jul  2 15:12:16 gateway SERVER[1240]: Dispatch_input: bad request line
> > 'BBXXXXXXXXXXXXXXXXXX%.176u%3
> > 00$nsecurity.%301$n%302$n%.192u%303$n\220\220\220\220\220\220\220\220\220\220\220\220\220\220\220\220\220\220\220\22

> These are for an application.  Not sure which or why 

See CERT Advisory CA-2000-22
	http://www.infowar.com/iwftp/cert/advisories/CA-2000-22.html

  "A popular replacement software package to the BSD lpd printing service
   called LPRng contains at least one software defect, known as a "format string
   vulnerability," which may allow remote users to execute arbitrary code on
   vulnerable systems."

  reply	other threads:[~2001-07-02 17:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-02 16:05 kernel
2001-07-02 16:11 ` Remco B. Brink
2001-07-02 16:16 ` Alan Cox
2001-07-02 17:42   ` Guest section DW [this message]
2001-07-02 19:51     ` kernel
2001-07-03  7:45       ` David Weinehall
2001-07-02 17:00 ` Richard B. Johnson
2001-07-02 18:23   ` [OT] " Ville Herva

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010702194212.A400@win.tue.nl \
    --to=dwguest@win.tue.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=enforcer@ddx.a2000.nu \
    --cc=kernel@ddx.a2000.nu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®