Bug 1316640 - Please update to 4.1.1 to fix an security bug.
Summary: Please update to 4.1.1 to fix an security bug.
Keywords:
Status: CLOSED DUPLICATE of bug 1315247
Alias: None
Product: Fedora
Classification: Fedora
Component: libotr
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-10 16:29 UTC by Frank Büttner
Modified: 2016-03-11 12:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-11 12:13:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Frank Büttner 2016-03-10 16:29:01 UTC
Description of problem:
Security update: libotr version 4.1.1

    Versions 4.1.0 and earlier of libotr in 64-bit builds contain an integer overflow security flaw. This flaw could potentially be exploited by a remote attacker to cause a heap buffer overflow and subsequently for arbitrary code to be executed on the user's machine.

    CVE-2016-2851 has been assigned to this issue.

    Please upgrade to libotr version 4.1.1 immediately.

    Users of libotr packages in Linux and *BSD distributions should see updated packages shortly.

    This security release includes the following updates:

        Fix an integer overflow bug that can cause a heap buffer overflow (and from there remote code execution) on 64-bit platforms
        Fix possible free() of an uninitialized pointer
        Be stricter about parsing v3 fragments
        Add a testsuite ("make check" to run it), but only on Linux for now, since it uses Linux-specific features such as epoll
        Fix a memory leak when reading a malformed instance tag file
        Protocol documentation clarifications

Version-Release number of selected component (if applicable):
libotr-4.1.0-2.fc23.x86_64

Comment 1 Paul Wouters 2016-03-11 12:13:52 UTC
All packages were already pushed before this email was created :)

See: https://bugzilla.redhat.com/show_bug.cgi?id=1315247

*** This bug has been marked as a duplicate of bug 1315247 ***


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