Jump to content
Compatible Support Forums
Sign in to follow this  
news

[slackware-security] lcms (SSA:2009-083-01)

Recommended Posts

 

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA1

 

[slackware-security] lcms (SSA:2009-083-01)

 

New lcms packages are available for Slackware 10.0, 10.1, 10.2, 11.0, 12.0,

12.1, 12.2, and -current to fix security issues.

 

More details about the issues may be found in the Common

Vulnerabilities and Exposures (CVE) database:

 

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0581

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0723

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0733

 

 

Here are the details from the Slackware 12.2 ChangeLog:

+--------------------------+

patches/packages/lcms-1.18-i486-1_slack12.2.tgz: Upgraded to lcms-1.18.

This update fixes security issues discovered in LittleCMS by Chris Evans.

These flaws could cause program crashes (denial of service) or the execution

of arbitrary code as the user of the lcms-linked program.

For more information, see:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0581

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0723

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0733

(* Security fix *)

+--------------------------+

 

 

Where to find the new packages:

+-----------------------------+

 

HINT: Getting slow download speeds from ftp.slackware.com?

Give slackware.osuosl.org a try. This is another primary FTP site

for Slackware that can be considerably faster than downloading

directly from ftp.slackware.com.

 

Thanks to the friendly folks at the OSU Open Source Lab

(http://osuosl.org) for donating additional FTP and rsync hosting

to the Slackware project! :-)

 

Also see the "Get Slack" section on http://slackware.com for

additional mirror sites near you.

 

Updated package for Slackware 10.0:

ftp://ftp.slackware.com/pub/slackware/slackware-10.0/patches/packages/lcms-1.18-i486-1_slack10.0.tgz

 

Updated package for Slackware 10.1:

ftp://ftp.slackware.com/pub/slackware/slackware-10.1/patches/packages/lcms-1.18-i486-1_slack10.1.tgz

 

Updated package for Slackware 10.2:

ftp://ftp.slackware.com/pub/slackware/slackware-10.2/patches/packages/lcms-1.18-i486-1_slack10.2.tgz

 

Updated package for Slackware 11.0:

ftp://ftp.slackware.com/pub/slackware/slackware-11.0/patches/packages/lcms-1.18-i486-1_slack11.0.tgz

 

Updated package for Slackware 12.0:

ftp://ftp.slackware.com/pub/slackware/slackware-12.0/patches/packages/lcms-1.18-i486-1_slack12.0.tgz

 

Updated package for Slackware 12.1:

ftp://ftp.slackware.com/pub/slackware/slackware-12.1/patches/packages/lcms-1.18-i486-1_slack12.1.tgz

 

Updated package for Slackware 12.2:

ftp://ftp.slackware.com/pub/slackware/slackware-12.2/patches/packages/lcms-1.18-i486-1_slack12.2.tgz

 

Updated package for Slackware -current:

ftp://ftp.slackware.com/pub/slackware/slackware-current/slackware/l/lcms-1.18-i486-1.tgz

 

 

MD5 signatures:

+-------------+

 

Slackware 10.0 package:

6a3369ac79791ca0999dbf57aed56207 lcms-1.18-i486-1_slack10.0.tgz

 

Slackware 10.1 package:

fbf182d254c740f688672713f64a17e5 lcms-1.18-i486-1_slack10.1.tgz

 

Slackware 10.2 package:

2d96b95ba90abca6af5da84727078fc7 lcms-1.18-i486-1_slack10.2.tgz

 

Slackware 11.0 package:

0814537987ca4994a4a331a3e47bcc98 lcms-1.18-i486-1_slack11.0.tgz

 

Slackware 12.0 package:

e6752bdf112b27d6c17758aaac7a02f6 lcms-1.18-i486-1_slack12.0.tgz

 

Slackware 12.1 package:

9f8b2abb83ac254bb4c0fe85e519b02a lcms-1.18-i486-1_slack12.1.tgz

 

Slackware 12.2 package:

70a303fa6a5aa390c09723153abf3589 lcms-1.18-i486-1_slack12.2.tgz

 

Slackware -current package:

9b9ee19b1b2b1ada4ae15044d7218365 lcms-1.18-i486-1.tgz

 

 

Installation instructions:

+------------------------+

 

Upgrade the package as root:

# upgradepkg lcms-1.18-i486-1_slack12.2.tgz

 

Then restart any daemons that are linked with lcms.

 

 

+-----+

 

Slackware Linux Security Team

http://slackware.com/gpg-key

security ( -at -) slackware.com

 

+------------------------------------------------------------------------+

 

Share this post


Link to post

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×