Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • aports aports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 657
    • Issues 657
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 334
    • Merge requests 334
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpine
  • aportsaports
  • Issues
  • #10811
Closed
Open
Created Sep 19, 2019 by Alicha CH@alichaReporter5 of 5 tasks completed5/5 tasks

poppler: integer overflow in JPXStream::init function leading to memory consumption (CVE-2019-9959)

The JPXStream::init function in Poppler 0.78.0 and earlier doesn't check for negative values of stream length, leading to an Integer Overflow, thereby making it possible to allocate a large memory chunk on the heap, with a size controlled by an attacker, as demonstrated by pdftocairo.

Fixed In Version:

poppler 0.79

References:

  • https://gitlab.freedesktop.org/poppler/poppler/blob/master/NEWS
  • https://nvd.nist.gov/vuln/detail/CVE-2019-9959
  • https://gitlab.freedesktop.org/poppler/poppler/issues/805

Patch:

https://gitlab.freedesktop.org/poppler/poppler/commit/68ef84e5968a4249c2162b839ca6d7975048a557

Affected branches:

  • master
  • 3.10-stable
  • 3.9-stable
  • 3.8-stable
  • 3.7-stable
Edited Sep 24, 2019 by Leonardo Arena
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking