Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
aports
aports
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 651
    • Issues 651
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 193
    • Merge Requests 193
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • alpine
  • aportsaports
  • Issues
  • #9611

Closed
Open
Opened Nov 01, 2018 by Alicha CH@alichaReporter
  • Report abuse
  • New issue
Report abuse New issue

[3.9] curl: Multiple vulnerabilities (CVE-2018-16839, CVE-2018-16840, CVE-2018-16842)

CVE-2018-16839: SASL password overflow via integer overflow

The internal function Curl_auth_create_plain_message fails to correctly verify that the passed in lengths
for name and password aren’t too long, then calculates a buffer size to allocate.

On systems with a 32 bit size_t, the math to calculate the buffer size triggers an integer overflow when the user name length exceeds 2GB (2^31 bytes).
This integer overflow usually causes a very small buffer to actually get allocated instead of the intended very huge one, making the use of that buffer end up in a heap buffer overflow.

Affected versions:

libcurl 7.33.0 to and including 7.61.1

Not affected versions:

libcurl < 7.33.0 and >= 7.62.0

Reference:

https://curl.haxx.se/docs/CVE-2018-16839.html

Patch:

https://github.com/curl/curl/commit/f3a24d7916b9173c69a3e0ee790102993833d6c5

CVE-2018-16840: use-after-free in handle close

When closing and cleaning up an “easy” handle in the Curl_close() function, the library code first frees a struct (without nulling the pointer) and might
then subsequently erroneously write to a struct field within that already freed struct.

Affected versions:

libcurl 7.59.0 to and including 7.61.1

Not affected versions:

libcurl < 7.59.0 and >= 7.62.0

Reference:

https://curl.haxx.se/docs/CVE-2018-16840.html

Patch:

https://github.com/curl/curl/commit/81d135d67155c5295b1033679c606165d4e28f3f

CVE-2018-16842: warning message out-of-buffer read

The command line tool has a generic function for displaying warning and informational messages to stderr for various
situations. For example if an unknown command line argument is used, or passed to it in a “config” file.

This display function formats the output to wrap at 80 columns. The wrap logic is however flawed, so if a single word in the message is itself longer than 80 bytes
the buffer arithmetic calculates the remainder wrong and will end up reading behind the end of the buffer. This could lead to information disclosure or crash.

Reference:

https://curl.haxx.se/docs/CVE-2018-16842.html

Patch:

https://github.com/curl/curl/commit/d530e92f59ae9bb2d47066c3c460b25d2ffeb211

(from redmine: issue id 9611, created on 2018-11-01, closed on 2018-11-08)

  • Relations:
    • parent #9610 (closed)
  • Changesets:
    • Revision 8776c8cc on 2018-11-05T08:17:04Z:
main/curl: security upgrade to 7.62.0

CVE-2018-16839, CVE-2018-16840, CVE-2018-16842

Fixes #9611
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
3.9.0
Milestone
3.9.0 (Past due)
Assign milestone
Time tracking
None
Due date
None
2
Labels
Normal type:bug
Assign labels
  • View project labels
Reference: alpine/aports#9611