Red Hat Security Advisory: LPRng contains a critical string format bug | Linux Today

Red Hat Security Advisory: LPRng contains a critical string format bug

Written By
Web Webster
Web Webster
Oct 4, 2000

Date: Wed, 4 Oct 2000 12:04:00 -0400
From: bugzilla@REDHAT.COM
To: BUGTRAQ@SECURITYFOCUS.COM
Subject: [RHSA-2000:065-04] LPRng contains a critical string format
bug


                   Red Hat, Inc. Security Advisory

Synopsis:          LPRng contains a critical string format bug
Advisory ID:       RHSA-2000:065-04
Issue date:        2000-09-26
Updated on:        2000-10-04
Product:           Red Hat Linux
Keywords:          LPRng security lpd printing lpr syslog
Cross references:  N/A

1. Topic:

LPRng has a string format bug in the use_syslog function which
could lead to root compromise.

2. Relevant releases/architectures:

Red Hat Linux 7.0 – i386

3. Problem description:

LPRng has a string format bug in the use_syslog function. This
function returns user input in a string that is passed to the
syslog() function as the format string. It is possible to corrupt
the print daemon’s execution with unexpected format specifiers,
thus gaining root access to the computer. The vulnerability is
theoretically exploitable both locally and remotely.

4. Solution:

For each RPM for your particular architecture, run:

rpm -Fvh [filename]

where filename is the name of the RPM.

5. Bug IDs fixed (http://bugzilla.redhat.com/bugzilla
for more info):

17756 – Critical security hole in LPRng, remote root

6. RPMs required:

Red Hat Linux 7.0:

i386:
ftp://updates.redhat.com/7.0/i386/LPRng-3.6.24-2.i386.rpm

sources:
ftp://updates.redhat.com/7.0/SRPMS/LPRng-3.6.24-2.src.rpm

7. Verification:

MD5 sum                           Package Name

c1fc795122b067dd9549aceb75bf5694 7.0/SRPMS/LPRng-3.6.24-2.src.rpm
05251e71ae5f2d2fdbc6611eea6f8651 7.0/i386/LPRng-3.6.24-2.i386.rpm

These packages are GPG signed by Red Hat, Inc. for security. Our
key is available at:
http://www.redhat.com/corp/contact.html

You can verify each package with the following command:
rpm –checksig <filename>

If you only wish to verify that each package has not been
corrupted or tampered with, examine only the md5sum with the
following command:
rpm –checksig –nogpg <filename>

8. References:

Originally reported to bugtraq by Chris Evans chris@scary.beasts.org on 25
Sep, 2000.

Copyright(c) 2000 Red Hat, Inc.

Web Webster

Web Webster

Web Webster has more than 20 years of writing and editorial experience in the tech sector. He’s written and edited news, demand generation, user-focused, and thought leadership content for business software solutions, consumer tech, and Linux Today, he edits and writes for a portfolio of tech industry news and analysis websites including webopedia.com, and DatabaseJournal.com.

Linux Today Logo

LinuxToday is a trusted, contributor-driven news resource supporting all types of Linux users. Our thriving international community engages with us through social media and frequent content contributions aimed at solving problems ranging from personal computing to enterprise-level IT operations. LinuxToday serves as a home for a community that struggles to find comparable information elsewhere on the web.

Property of TechnologyAdvice. © 2026 TechnologyAdvice. All Rights Reserved

Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.