Bug 432471 (CVE-2008-0667) - CVE-2008-0667 acroread: silent print vulnerability
Summary: CVE-2008-0667 acroread: silent print vulnerability
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2008-0667
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL: http://nvd.nist.gov/nvd.cfm?cvename=C...
Whiteboard:
Depends On: 432657 432658 432659
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-12 07:59 UTC by Tomas Hoger
Modified: 2019-09-29 12:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-21 09:36:58 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2008:0144 0 normal SHIPPED_LIVE Critical: acroread security update 2008-02-22 16:57:24 UTC

Description Tomas Hoger 2008-02-12 07:59:49 UTC
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 09:36:58 UTC
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.