From: glsamaker@gentoo.org
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202209-21 ] Poppler: Arbitrary Code Execution
Date: Thu, 29 Sep 2022 14:24:01 -0000 [thread overview]
Message-ID: <166446144201.9.2106576169389467735@90bb6a0775af> (raw)
[-- Attachment #1: Type: text/plain, Size: 2477 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 202209-21
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: High
Title: Poppler: Arbitrary Code Execution
Date: September 29, 2022
Bugs: #867958
ID: 202209-21
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A vulnerability has been discovered in Poppler which could allow for
arbitrary code execution.
Background
==========
Poppler is a PDF rendering library based on the xpdf-3.0 code base.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 app-text/poppler < 22.09.0 >= 22.09.0
Description
===========
Multiple vulnerabilities have been discovered in Poppler. Please review
the CVE identifiers referenced below for details.
Impact
======
Processing a specially crafted PDF file or JBIG2 image could lead to a
crash or the execution of arbitrary code.
Workaround
==========
Avoid opening untrusted PDFs.
Resolution
==========
All Poppler users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-text/poppler-22.09.0"
References
==========
[ 1 ] CVE-2021-30860
https://nvd.nist.gov/vuln/detail/CVE-2021-30860
[ 2 ] CVE-2022-38784
https://nvd.nist.gov/vuln/detail/CVE-2022-38784
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202209-21
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 2022 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:[~2022-09-29 14:40 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=166446144201.9.2106576169389467735@90bb6a0775af \
--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