Bug 432471 - (CVE-2008-0667) CVE-2008-0667 acroread: silent print vulnerability
CVE-2008-0667 acroread: silent print vulnerability
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
http://nvd.nist.gov/nvd.cfm?cvename=C...
source=cve,reported=20080211,public=2...
: Security
Depends On: 432657 432658 432659
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-12 02:59 EST by Tomas Hoger
Modified: 2008-07-21 05:36 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-21 05:36:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tomas Hoger 2008-02-12 02:59:49 EST
Common Vulnerabilities and Exposures assigned an identifier CVE-2008-0667 to the following vulnerability:

The DOC.print function in the Adobe JavaScript API, as used by Adobe
Acrobat and Reader before 8.1.2, allows remote attackers to configure
silent non-interactive printing, and trigger the printing of an
arbitrary number of copies of a document.  NOTE: this issue might be
subsumed by CVE-2008-0655.

References:
http://www.securityfocus.com/archive/1/archive/1/487760/100/0/threaded
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403079&sliceId=1
http://www.fortiguardcenter.com/advisory/FGA-2008-04.html
http://www.adobe.com/support/security/advisories/apsa08-01.html
http://www.securityfocus.com/bid/27641
http://www.frsirt.com/english/advisories/2008/0425/references
http://secunia.com/advisories/28802
http://secunia.com/advisories/28851
Comment 3 Red Hat Product Security 2008-07-21 05:36:58 EDT
This issue was addressed in:

Red Hat Enterprise Linux Extras:
  http://rhn.redhat.com/errata/RHSA-2008-0144.html


Note You need to log in before you can comment on or make changes to this bug.