LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-20-2018, 06:43 AM   #751
elcore
Member
 
Registered: Sep 2014
Distribution: Slackware
Posts: 492

Rep: Reputation: Disabled

Apparently, OpenBSD has got rid of Intel HyperThreading due to Spectre. (It's no problem to get rid of it on amd64, I've had this disabled in my kernels for couple of years now)

Last edited by elcore; 06-20-2018 at 06:46 AM.
 
Old 06-25-2018, 10:10 AM   #752
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 456

Rep: Reputation: 233Reputation: 233Reputation: 233
Quote:
Originally Posted by elcore View Post
Apparently, OpenBSD has got rid of Intel HyperThreading due to Spectre. (It's no problem to get rid of it on amd64, I've had this disabled in my kernels for couple of years now)
It looks like a new type of cache timing attack dubbed TLBleed:
https://www.theregister.co.uk/2018/0...yperthreading/
https://www.theregister.co.uk/2018/0...key_data_leak/
The details will be revealed in a few days at the BlackHat 2018 conference:
https://www.blackhat.com/us-18/brief...t-enough-10149
 
2 members found this post helpful.
Old 07-11-2018, 12:13 AM   #753
Thom1b
Member
 
Registered: Mar 2010
Location: France
Distribution: Slackware
Posts: 208

Rep: Reputation: 155Reputation: 155
bind-9.10.8 is released with security fixes.

Quote:
Security Fixes

When recursion is enabled but the allow-recursion and allow-query-cache ACLs are not specified, they should be limited to local networks, but they were inadvertently set to match the default allow-query, thus allowing remote queries. This flaw is disclosed in CVE-2018-5738. [GL #309]

Last edited by Thom1b; 07-11-2018 at 01:23 AM. Reason: Wrong version : s/9.11.4/9.10.8
 
1 members found this post helpful.
Old 07-11-2018, 01:26 AM   #754
Thom1b
Member
 
Registered: Mar 2010
Location: France
Distribution: Slackware
Posts: 208

Rep: Reputation: 155Reputation: 155
curl-7.61.0 is released with one security fix:
Quote:
SMTP send heap buffer overflow
==============================

Project curl Security Advisory, July 11th 2018 -
[Permalink](https://curl.haxx.se/docs/adv_2018-70a2.html)

VULNERABILITY
-------------

curl might overflow a heap based memory buffer when sending data over SMTP and
using a reduced read buffer.

When sending data over SMTP, curl allocates a separate "scratch area" on the
heap to be able to escape the uploaded data properly if the uploaded data
contains data that requires it.

The size of this temporary scratch area was mistakenly made to be `2 *
sizeof(download_buffer)` when it should have been made `2 *
sizeof(upload_buffer)`.

The upload and the download buffer sizes are identically sized by default
(16KB) but since version 7.54.1, curl can resize the download buffer into a
smaller buffer (as well as larger). If the download buffer size is set to a
value smaller than 10923, the `Curl_smtp_escape_eob()` function might overflow
the scratch buffer when sending contents of sufficient size and contents.

The curl command line tool lowers the buffer size when `--limit-rate` is set
to a value smaller than 16KB.

We are not aware of any exploit of this flaw.

TEST CASES
----------
Here's a shell script

# Setup an SMTP end-point, make file, run curl
$ printf '220 Hi\n250 SIZE 10000\n250 OK\n250 OK\n354 send data\n' | nc -l -p 2525 >/dev/null &
$ printf '%5000s' > mail.txt
$ curl -v smtp://localhost:2525 --mail-from me --mail-rcpt root@localhost --upload-file mail.txt --limit-rate 1024

PHP code:

<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "smtp://localhost:2525");
curl_setopt($ch, CURLOPT_BUFFERSIZE, 1024);
curl_setopt($ch, CURLOPT_UPLOAD, 1);
curl_setopt($ch, CURLOPT_MAIL_FROM, "me");
curl_setopt($ch, CURLOPT_MAIL_RCPT, ["root@localhost"]);
curl_setopt($ch, CURLOPT_VERBOSE, 1);
$eof = false;
curl_setopt($ch, CURLOPT_READFUNCTION, function($ch, $stream, $maxSize) {
global $eof;
echo "Max Size: [$maxSize]\n";
if ($eof) {
return "";
}
$eof = true;
return str_repeat(" ", $maxSize);
});
curl_exec($ch);
curl_close($ch);

INFO
----

This bug was introduced in April 2017 in [this
commit](https://github.com/curl/curl/commit/e40e9d7f0decc79) when we
introduced support for buffer resize. The scratch buffer was mistakenly made
to use the dynamic size when it should kept using the fixed upload buffer
size.

The Common Vulnerabilities and Exposures (CVE) project has assigned the name
CVE-2018-0500 to this issue.

CWE-122: Heap-based Buffer Overflow

AFFECTED VERSIONS
-----------------

- Affected versions: curl 7.54.1 to and including curl 7.60.0
- Not affected versions: curl < 7.54.1 and curl >= 7.61.0

libcurl is used by many applications, but not always advertised as such.

THE SOLUTION
------------

In curl version 7.61.0, curl will use the upload buffer size as base for the
scratch area allocation.

A [patch for CVE-2018-0500](https://github.com/curl/curl/commit/ba1dbd78e5f1e.patch) is
available.

RECOMMENDATIONS
---------------

We suggest you take one of the following actions immediately, in order of
preference:

A - Upgrade curl to version 7.61.0

B - Apply the patch to your version and rebuild

C - Avoid using SMTP uploads with CURLOPT_BUFFERSIZE set below 10923
 
2 members found this post helpful.
Old 07-11-2018, 04:24 PM   #755
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 456

Rep: Reputation: 233Reputation: 233Reputation: 233
New Spectre Variant dubbed Bounds Check Bypass Store - CVE-2018-3693
https://cve.mitre.org/cgi-bin/cvenam...=CVE-2018-3693
Intel's Security Advisory:
https://01.org/security/advisories/intel-oss-10002
Research Paper:
https://people.csail.mit.edu/vlk/spectre11.pdf
It looks to be a sub-variant of: CVE-2017-5753 aka Spectre Variant 1
Not yet listed in the capabilities of the spectre-meltdown-checker:
https://github.com/speed47/spectre-meltdown-checker

Intel's latest white paper release suggest SW mitigation (kernel):
https://software.intel.com/sites/def...hite-Paper.pdf
 
3 members found this post helpful.
Old 07-16-2018, 01:18 PM   #756
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,345

Rep: Reputation: 3118Reputation: 3118Reputation: 3118Reputation: 3118Reputation: 3118Reputation: 3118Reputation: 3118Reputation: 3118Reputation: 3118Reputation: 3118Reputation: 3118
mutt 1.10.1 released

With important security fixes. Quoting the message from Kevin J. McCarthy on the mutt-announce mailing list:
Quote:
This is a bug fix release, and includes a few important security fixes. I strongly recommend IMAP and POP users upgrade as soon as possible.
Thanks to Jude DaShiell for the heads up.

Last edited by Didier Spaier; 07-16-2018 at 01:48 PM.
 
1 members found this post helpful.
  


Reply

Tags
exploit, security, slackware


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[Slackware Security]: Some pending vulnerabilities... mancha Slackware 7 08-22-2013 09:08 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:37 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration