Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Monday October 19 2015, @11:05PM   Printer-friendly
from the found-and-fixed dept.

What they've found is that there's a companion memory leak (CVE-2015-5333) and buffer overflow (CVE-2015-5334) in the SSL replacement candidate.

The researchers from Qualys (their notice published here) said they were trying to see if a remote code execution attack is feasible against vulnerabilities they've turned up in OpenSMTPD (which earlier this month hit version 5.7.3).

“Because we could not find one in OpenSMTPD itself, we started to review the malloc()s and free()s of its libraries, and eventually found a memory leak in LibreSSL's OBJ_obj2txt() function; we then realized that this function also contains a buffer overflow (an off-by-one, usually stack-based).”

The memory leak provides a path for an attacker to cause a denial-of-service attack, and also permits triggering of the buffer overflow.

The LibreSSL team has released fixes for OpenBSD.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by TheRaven on Tuesday October 20 2015, @04:46PM

    by TheRaven (270) on Tuesday October 20 2015, @04:46PM (#252364) Journal
    Every point that you make is either true of all languages that run on a *NIX system, not true of C++11, or not true for the last decade or so.
    --
    sudo mod me up
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by NCommander on Wednesday October 21 2015, @07:21AM

    by NCommander (2) Subscriber Badge <michael@casadevall.pro> on Wednesday October 21 2015, @07:21AM (#252625) Homepage Journal

    Can you cite actual examples disproving my claims? I like being proven wrong, but I'm not going to be dissuaded by "its no longer true".

    I've had to work with a C++14 codebase as of late, and most of the pain is still there, and a lot of other headaches (templates for one) are still a core part of the language, made worse by the fact that all the new stuff is dependent on templates.

    --
    Still always moving