From: glsamaker@gentoo.org
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202409-25 ] Xpdf: Multiple Vulnerabilities
Date: Wed, 25 Sep 2024 06:30:13 -0000 [thread overview]
Message-ID: <172724581355.7.18186997623284111257@3f85d36892cf> (raw)
[-- Attachment #1: Type: text/plain, Size: 3675 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 202409-25
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: Xpdf: Multiple Vulnerabilities
Date: September 25, 2024
Bugs: #845027, #908037, #936407
ID: 202409-25
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Multiple vulnerabilities have been found in Xpdf, the worst of which
could result in denial of service.
Background
==========
Xpdf is an X viewer for PDF files.
Affected packages
=================
Package Vulnerable Unaffected
------------- ------------ ------------
app-text/xpdf < 4.05 >= 4.05
Description
===========
Multiple vulnerabilities have been discovered in Xpdf. Please review the
CVE identifiers referenced below for details.
Impact
======
Please review the referenced CVE identifiers for details.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All Xpdf users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-text/xpdf-4.05"
References
==========
[ 1 ] CVE-2018-7453
https://nvd.nist.gov/vuln/detail/CVE-2018-7453
[ 2 ] CVE-2018-16369
https://nvd.nist.gov/vuln/detail/CVE-2018-16369
[ 3 ] CVE-2022-30524
https://nvd.nist.gov/vuln/detail/CVE-2022-30524
[ 4 ] CVE-2022-30775
https://nvd.nist.gov/vuln/detail/CVE-2022-30775
[ 5 ] CVE-2022-33108
https://nvd.nist.gov/vuln/detail/CVE-2022-33108
[ 6 ] CVE-2022-36561
https://nvd.nist.gov/vuln/detail/CVE-2022-36561
[ 7 ] CVE-2022-38222
https://nvd.nist.gov/vuln/detail/CVE-2022-38222
[ 8 ] CVE-2022-38334
https://nvd.nist.gov/vuln/detail/CVE-2022-38334
[ 9 ] CVE-2022-38928
https://nvd.nist.gov/vuln/detail/CVE-2022-38928
[ 10 ] CVE-2022-41842
https://nvd.nist.gov/vuln/detail/CVE-2022-41842
[ 11 ] CVE-2022-41843
https://nvd.nist.gov/vuln/detail/CVE-2022-41843
[ 12 ] CVE-2022-41844
https://nvd.nist.gov/vuln/detail/CVE-2022-41844
[ 13 ] CVE-2022-43071
https://nvd.nist.gov/vuln/detail/CVE-2022-43071
[ 14 ] CVE-2022-43295
https://nvd.nist.gov/vuln/detail/CVE-2022-43295
[ 15 ] CVE-2022-45586
https://nvd.nist.gov/vuln/detail/CVE-2022-45586
[ 16 ] CVE-2022-45587
https://nvd.nist.gov/vuln/detail/CVE-2022-45587
[ 17 ] CVE-2023-2662
https://nvd.nist.gov/vuln/detail/CVE-2023-2662
[ 18 ] CVE-2023-2663
https://nvd.nist.gov/vuln/detail/CVE-2023-2663
[ 19 ] CVE-2023-2664
https://nvd.nist.gov/vuln/detail/CVE-2023-2664
[ 20 ] CVE-2023-3044
https://nvd.nist.gov/vuln/detail/CVE-2023-3044
[ 21 ] CVE-2023-3436
https://nvd.nist.gov/vuln/detail/CVE-2023-3436
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202409-25
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.
License
=======
Copyright 2024 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
https://creativecommons.org/licenses/by-sa/2.5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-09-25 6:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=172724581355.7.18186997623284111257@3f85d36892cf \
--to=glsamaker@gentoo.org \
--cc=gentoo-announce@lists.gentoo.org \
--cc=security@gentoo.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