<vuln vid="29d34524-0542-11e9-a444-080027fee39c">
<topic>gitea -- privilege escalation, XSS</topic>
<affects>
<package>
<name>gitea</name>
<range><lt>1.6.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Gitea project reports:</p>
<blockquote cite="https://github.com/go-gitea/gitea/releases/tag/v1.6.2">
<p>Security</p>
<ul>
<li>Sanitize uploaded file names</li>
<li>HTMLEncode user added text</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/go-gitea/gitea/issues/5569</url>
<url>https://github.com/go-gitea/gitea/issues/5565</url>
</references>
<dates>
<discovery>2018-12-19</discovery>
<entry>2018-12-21</entry>
</dates>
</vuln>
<vuln vid="f8fe2905-0918-11e9-a550-00262d164c21">
<topic>rpm4 -- regression in -setperms, -setugids and -restore</topic>
<affects>
<package>
<name>rpm4</name>
<range><lt>4.14.2.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>rpm4 reports:</p>
<blockquote cite="http://rpm.org/wiki/Releases/4.14.2.1">
<p>Regression in -setperms, -setugids and -restore</p>
<p>Note that this update can not automatically fix possible damage
done by using -setperms, -setugids or -restore with rpm 4.14.2, it
merely fixes the functionlity itself. Any damage needs to be
investigated and fixed manually, such as using -verify and -restore
or reinstalling packages.</p>
</blockquote>
</body>
</description>
<references>
<url>http://rpm.org/wiki/Releases/4.14.2.1</url>
</references>
<dates>
<discovery>2018-10-22</discovery>
<entry>2018-12-26</entry>
</dates>
</vuln>
<vuln vid="70b774a8-05bc-11e9-87ad-001b217b3468">
<topic>Gitlab -- Arbitrary File read in Gitlab project import</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>11.5.0</ge><lt>11.5.5</lt></range>
<range><ge>11.4.0</ge><lt>11.4.12</lt></range>
<range><ge>8.9.0</ge><lt>11.3.14</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/12/20/critical-security-release-gitlab-11-dot-5-dot-5-released">
<p>Arbitrary File read in Gitlab project import</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/12/20/critical-security-release-gitlab-11-dot-5-dot-5-released/</url>
<cvename>CVE-2018-20229</cvename>
</references>
<dates>
<discovery>2018-12-20</discovery>
<entry>2018-12-22</entry>
</dates>
</vuln>
<vuln vid="4f8665d0-0465-11e9-b77a-6cc21735f730">
<topic>shibboleth-sp -- crashes on malformed date/time content</topic>
<affects>
<package>
<name>shibboleth-sp</name>
<range><ge>3.0.0</ge><lt>3.0.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Shibboleth Consortium reports:</p>
<blockquote cite="https://shibboleth.net/community/advisories/secadv_20181219a.txt">
<p>SAML messages, assertions, and metadata all commonly contain
date/time information in a standard XML format.</p>
<p>Invalid formatted data in such fields cause an exception of a type
that was not handled properly in the V3 software and causes a crash
(usually to the shibd daemon process, but possibly to Apache in rare
cases). Note that the crash occurs prior to evaluation of a message's
authenticity, so can be exploited by an untrusted attacker.</p>
<p>The problem is believed to be specific to the V3 software and would
not cause a crash in the older, now unsupported, V2 software.</p>
</blockquote>
</body>
</description>
<references>
<url>https://shibboleth.net/community/advisories/secadv_20181219a.txt</url>
</references>
<dates>
<discovery>2018-12-19</discovery>
<entry>2018-12-20</entry>
</dates>
</vuln>
<vuln vid="1999a215-fc6b-11e8-8a95-ac1f6b67e138">
<topic>couchdb -- administrator privilege escalation</topic>
<affects>
<package>
<name>couchdb</name>
<range><lt>2.3.0,2</lt></range>
</package>
<package>
<name>couchdb2</name>
<range><lt>2.3.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Apache CouchDB PMC reports:</p>
<blockquote cite="https://lists.apache.org/thread.html/...">
<p>Database Administrator could achieve privilege escalation to
the account that CouchDB runs under, by abusing insufficient validation
in the HTTP API, escaping security controls implemented in previous
releases.</p>
</blockquote>
</body>
</description>
<references>
<url>http://docs.couchdb.org/en/stable/cve/2018-17188.html</url>
<cvename>CVE-2018-17188</cvename>
</references>
<dates>
<discovery>2018-12-01</discovery>
<entry>2018-12-13</entry>
</dates>
</vuln>
<vuln vid="b80f039d-579e-4b82-95ad-b534a709f220">
<topic>bro -- "Magellan" remote code execution vulnerability in bundled sqlite</topic>
<affects>
<package>
<name>bro</name>
<range><lt>2.6.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Bro Network security Monitor reports:</p>
<blockquote cite="https://www.bro.org/download/NEWS.bro.html">
<p>Bro 2.6.1 updates the embedded SQLite to version 3.26.0
to address the "Magellan" remote code execution vulnerability.
The stock Bro configuration/scripts don't use SQLite by
default, but custom user scripts/packages may.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.bro.org/download/NEWS.bro.html</url>
</references>
<dates>
<discovery>2018-12-01</discovery>
<entry>2018-12-20</entry>
</dates>
</vuln>
<vuln vid="fa6a4a69-03d1-11e9-be12-a4badb2f4699">
<topic>FreeBSD -- bootpd buffer overflow</topic>
<affects>
<package>
<name>FreeBSD</name>
<range><ge>12.0</ge><lt>12.0_1</lt></range>
<range><ge>11.2</ge><lt>11.2_7</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>Due to insufficient validation of network-provided data
it may be possible for a malicious attacker to craft a bootp
packet which could cause a stack buffer overflow.</p>
<h1>Impact:</h1>
<p>It is possible that the buffer overflow could lead to a
Denial of Service or remote code execution.</p>
</body>
</description>
<references>
<cvename>CVE-2018-1716</cvename>
<freebsdsa>SA-18:15.bootpd</freebsdsa>
</references>
<dates>
<discovery>2018-12-19</discovery>
<entry>2018-12-19</entry>
</dates>
</vuln>
<vuln vid="4b98613c-0078-11e9-b05b-00e04c1ea73d">
<topic>wordpress -- multiple issues</topic>
<affects>
<package>
<name>wordpress</name>
<name>fr-wordpress</name>
<range><lt>5.0.1,1</lt></range>
</package>
<package>
<name>de-wordpress</name>
<name>zh_CN-wordpress</name>
<name>zh_TW-wordpress</name>
<name>ja-wordpress</name>
<name>ru-wordpress</name>
<range><lt>5.0.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>wordpress developers reports:</p>
<blockquote cite="https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/">
<p>WordPress versions 5.0 and earlier are affected by the following bugs, which are
fixed in version 5.0.1. Updated versions of WordPress 4.9 and older releases are
also available, for users who have not yet updated to 5.0.</p>
<p>Karim El Ouerghemmi discovered that authors could alter meta data to delete files
that they weren’t authorized to.</p>
<p>Simon Scannell of RIPS Technologies discovered that authors could create posts of
unauthorized post types with specially crafted input.</p>
<p>Sam Thomas discovered that contributors could craft meta data in a way that resulted
in PHP object injection.</p>
<p>Tim Coen discovered that contributors could edit new comments from higher-privileged
users, potentially leading to a cross-site scripting vulnerability.</p>
<p>Tim Coen also discovered that specially crafted URL inputs could lead to a cross-site
scripting vulnerability in some circumstances. WordPress itself was not affected,
but plugins could be in some situations.</p>
<p>Team Yoast discovered that the user activation screen could be indexed by search
engines in some uncommon configurations, leading to exposure of email addresses,
and in some rare cases, default generated passwords.</p>
<p>Tim Coen and Slavco discovered that authors on Apache-hosted sites could upload
specifically crafted files that bypass MIME verification, leading to a cross-site
scripting vulnerability.</p>
</blockquote>
</body>
</description>
<references>
<url>https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/</url>
</references>
<dates>
<discovery>2018-12-13</discovery>
<entry>2018-12-15</entry>
</dates>
</vuln>
<vuln vid="293f40a0-ffa1-11e8-b258-0011d823eebd">
<topic>Mbed TLS -- Local timing attack on RSA decryption</topic>
<affects>
<package>
<name>mbedtls</name>
<range><lt>2.14.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Janos Follath reports:</p>
<blockquote cite="https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2018-03">
<p>An attacker who can run code on the same machine that is
performing an RSA decryption can potentially recover the plaintext
through a Bleichenbacher-like oracle.</p>
</blockquote>
</body>
</description>
<references>
<url>https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2018-03</url>
<cvename>CVE-2018-19608</cvename>
</references>
<dates>
<discovery>2018-11-28</discovery>
<entry>2018-12-14</entry>
</dates>
</vuln>
<vuln vid="bab29816-ff93-11e8-b05b-00e04c1ea73d">
<topic>typo3 -- multiple vulnerabilities</topic>
<affects>
<package>
<name>typo3-8</name>
<range><lt>8.7.21</lt></range>
</package>
<package>
<name>typo3-9</name>
<range><lt>9.5.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Typo3 core team reports:</p>
<blockquote cite="https://typo3.org/article/typo3-952-8721-and-7632-security-releases-published/">
<p>CKEditor 4.11 fixes an XSS vulnerability in the HTML parser reported by maxarr.
The vulnerability stemmed from the fact that it was possible to execute XSS inside
the CKEditor source area after persuading the victim to: (i) switch CKEditor to
source mode, then (ii) paste a specially crafted HTML code, prepared by the attacker,
into the opened CKEditor source area, and (iii) switch back to WYSIWYG mode.
Although this is an unlikely scenario, we recommend to upgrade to the latest editor version.</p>
<p>Failing to properly encode user input, online media asset rendering
(*.youtube and *.vimeo files) is vulnerable to cross-site scripting. A valid backend user
account or write access on the server system (e.g. SFTP) is needed in order to exploit this
vulnerability.</p>
<p>Failing to properly encode user input, notifications shown in modal windows in the TYPO3
backend are vulnerable to cross-site scripting. A valid backend user account is needed in
order to exploit this vulnerability.</p>
<p>Failing to properly encode user input, login status display is vulnerable to cross-site
scripting in the website frontend. A valid user account is needed in order to exploit this
vulnerability - either a backend user or a frontend user having the possibility to modify
their user profile.</p>
<p>Template patterns that are affected are:</p>
<ul>
<li>###FEUSER_[fieldName]### using system extension felogin</li>
<li><!--###USERNAME###--> for regular frontend rendering
(pattern can be defined individually using TypoScript setting
config.USERNAME_substToken)</li>
</ul>
<p>It has been discovered that cookies created in the Install Tool are not hardened to be
submitted only via HTTP. In combination with other vulnerabilities such as cross-site
scripting it can lead to hijacking an active and valid session in the Install Tool.</p>
<p>The Install Tool exposes the current TYPO3 version number to non-authenticated users.</p>
<p>Online Media Asset Handling (*.youtube and *.vimeo files) in the TYPO3 backend is vulnerable
to denial of service. Putting large files with according file extensions results in high
consumption of system resources. This can lead to exceeding limits of the current PHP process
which results in a dysfunctional backend component. A valid backend user account or write
access on the server system (e.g. SFTP) is needed in order to exploit this vulnerability.</p>
<p>TYPO3’s built-in record registration functionality (aka “basic shopping cart”) using recs
URL parameters is vulnerable to denial of service. Failing to properly ensure that anonymous
user sessions are valid, attackers can use this vulnerability in order to create an arbitrary
amount of individual session-data records in the database.</p>
</blockquote>
</body>
</description>
<references>
<url>https://typo3.org/article/typo3-952-8721-and-7632-security-releases-published/</url>
</references>
<dates>
<discovery>2018-12-11</discovery>
<entry>2018-12-14</entry>
</dates>
</vuln>
<vuln vid="757e6ee8-ff91-11e8-a148-001b217b3468">
<topic>Gitlab -- Arbitrary File read in GitLab project import with Git LFS</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>11.5.0</ge><lt>11.5.4</lt></range>
<range><ge>11.4.0</ge><lt>11.4.11</lt></range>
<range><ge>11.0.0</ge><lt>11.4.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/12/13/critical-security-release-gitlab-11-dot-5-dot-4-released/">
<p>Arbitrary File read in GitLab project import with Git LFS</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/12/13/critical-security-release-gitlab-11-dot-5-dot-4-released/</url>
<cvename>CVE-2018-20144</cvename>
</references>
<dates>
<discovery>2018-12-13</discovery>
<entry>2018-12-14</entry>
</dates>
</vuln>
<vuln vid="ed10ed3f-fddc-11e8-94cf-6805ca0b3d42">
<topic>phpMyAdmin -- multiple vulnerabilities</topic>
<affects>
<package>
<name>phpMyAdmin</name>
<name>phpMyAdmin-php56</name>
<name>phpMyAdmin-php70</name>
<name>phpMyAdmin-php71</name>
<name>phpMyAdmin-php72</name>
<range><lt>4.8.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The phpMyAdmin development team reports:</p>
<blockquote cite="https://www.phpmyadmin.net/security/PMASA-2018-6/">
<h3>Summary</h3>
<p>Local file inclusion through transformation feature</p>
<h3>Description</h3>
<p>A flaw has been found where an attacker can exploit
phpMyAdmin to leak the contents of a local file. The
attacker must have access to the phpMyAdmin Configuration
Storage tables, although these can easily be created in any
database to which the attacker has access. An attacker must
have valid credentials to log in to phpMyAdmin; this
vulnerability does not allow an attacker to circumvent the
login system.</p>
<h3>Severity</h3>
<p>We consider this vulnerability to be severe.</p>
</blockquote>
<blockquote cite="https://www.phpmyadmin.net/security/PMASA-2018-7/">
<h3>Summary</h3>
<p>XSRF/CSRF vulnerability in phpMyAdmin</p>
<h3>Description</h3>
<p>By deceiving a user to click on a crafted URL, it is
possible to perform harmful SQL operations such as renaming
databases, creating new tables/routines, deleting designer
pages, adding/deleting users, updating user passwords,
killing SQL processes, etc.</p>
<h3>Severity</h3>
<p>We consider this vulnerability to be of moderate severity.</p>
</blockquote>
<blockquote cite="https://www.phpmyadmin.net/security/PMASA-2018-8/">
<h3>Summary</h3>
<p>XSS vulnerability in navigation tree</p>
<h3>Description</h3>
<p>A Cross-Site Scripting vulnerability was found in the
navigation tree, where an attacker can deliver a payload to
a user through a specially-crafted database/table name.</p>
<h3>Severity</h3>
<p>We consider this attack to be of moderate severity.</p>
<h3>Mitigation factor</h3>
<p>The stored XSS vulnerabilities can be triggered only by
someone who logged in to phpMyAdmin, as the usual token
protection prevents non-logged-in users from accessing the
required forms.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.phpmyadmin.net/security/PMASA-2018-6/</url>
<url>https://www.phpmyadmin.net/security/PMASA-2018-7/</url>
<url>https://www.phpmyadmin.net/security/PMASA-2018-8/</url>
</references>
<dates>
<discovery>2018-12-11</discovery>
<entry>2018-12-12</entry>
</dates>
</vuln>
<vuln vid="d10b49b2-8d02-49e8-afde-0844626317af">
<topic>mozilla -- multiple vulnerabilities</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>64.0_3,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.2.6</lt></range>
</package>
<package>
<name>seamonkey</name>
<name>linux-seamonkey</name>
<range><lt>2.53.0</lt></range>
</package>
<package>
<name>firefox-esr</name>
<range><lt>60.4.0,1</lt></range>
</package>
<package>
<name>linux-firefox</name>
<range><lt>60.4.0,2</lt></range>
</package>
<package>
<name>libxul</name>
<name>thunderbird</name>
<name>linux-thunderbird</name>
<range><lt>60.4.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/">
<p>CVE-2018-12407: Buffer overflow with ANGLE library when using VertexBuffer11 module</p>
<p>CVE-2018-17466: Buffer overflow and out-of-bounds read in ANGLE library with TextureStorage11</p>
<p>CVE-2018-18492: Use-after-free with select element</p>
<p>CVE-2018-18493: Buffer overflow in accelerated 2D canvas with Skia</p>
<p>CVE-2018-18494: Same-origin policy violation using location attribute and performance.getEntries to steal cross-origin URLs</p>
<p>CVE-2018-18495: WebExtension content scripts can be loaded in about: pages</p>
<p>CVE-2018-18496: Embedded feed preview page can be abused for clickjacking</p>
<p>CVE-2018-18497: WebExtensions can load arbitrary URLs through pipe separators</p>
<p>CVE-2018-18498: Integer overflow when calculating buffer sizes for images</p>
<p>CVE-2018-12406: Memory safety bugs fixed in Firefox 64</p>
<p>CVE-2018-12405: Memory safety bugs fixed in Firefox 64 and Firefox ESR 60.4</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-12405</cvename>
<cvename>CVE-2018-12406</cvename>
<cvename>CVE-2018-12407</cvename>
<cvename>CVE-2018-17466</cvename>
<cvename>CVE-2018-18492</cvename>
<cvename>CVE-2018-18493</cvename>
<cvename>CVE-2018-18494</cvename>
<cvename>CVE-2018-18495</cvename>
<cvename>CVE-2018-18496</cvename>
<cvename>CVE-2018-18497</cvename>
<cvename>CVE-2018-18498</cvename>
<url>https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/</url>
<url>https://www.mozilla.org/en-US/security/advisories/mfsa2018-30/</url>
</references>
<dates>
<discovery>2018-12-11</discovery>
<entry>2018-12-11</entry>
<modified>2019-07-23</modified>
</dates>
</vuln>
<vuln vid="32498c8f-fc84-11e8-be12-a4badb2f4699">
<topic>FreeBSD -- Insufficient bounds checking in bhyve(8) device model</topic>
<affects>
<package>
<name>FreeBSD</name>
<range><ge>11.2</ge><lt>11.2_6</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>Insufficient bounds checking in one of the device models
provided by bhyve(8) can permit a guest operating system
to overwrite memory in the bhyve(8) processing possibly
permitting arbitary code execution.</p>
<h1>Impact:</h1>
<p>A guest OS using a firmware image can cause the bhyve
process to crash, or possibly execute arbitrary code on the
host as root.</p>
</body>
</description>
<references>
<cvename>CVE-2018-1716</cvename>
<freebsdsa>SA-18:14.bhyve</freebsdsa>
</references>
<dates>
<discovery>2018-12-04</discovery>
<entry>2018-12-10</entry>
</dates>
</vuln>
<vuln vid="268a4289-fc84-11e8-be12-a4badb2f4699">
<topic>FreeBSD -- Multiple vulnerabilities in NFS server code</topic>
<affects>
<package>
<name>FreeBSD</name>
<range><ge>11.2</ge><lt>11.2_5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>Insufficient and improper checking in the NFS server
code could cause a denial of service or possibly remote
code execution via a specially crafted network packet.</p>
<h1>Impact:</h1>
<p>A remote attacker could cause the NFS server to crash,
resulting in a denial of service, or possibly execute
arbitrary code on the server.</p>
</body>
</description>
<references>
<cvename>CVE-2018-1715</cvename>
<freebsdsa>SA-18:13.nfs</freebsdsa>
</references>
<dates>
<discovery>2018-11-27</discovery>
<entry>2018-12-10</entry>
</dates>
</vuln>
<vuln vid="2a86f45a-fc3c-11e8-a414-00155d006b02">
<topic>node.js -- multiple vulnerabilities</topic>
<affects>
<package>
<name>node6</name>
<range><lt>6.15.0</lt></range>
</package>
<package>
<name>node8</name>
<range><lt>8.14.0</lt></range>
</package>
<package>
<name>node10</name>
<range><lt>10.14.0</lt></range>
</package>
<package>
<name>node</name>
<range><lt>11.3.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Node.js reports:</p>
<blockquote cite="https://nodejs.org/en/blog/vulnerability/november-2018-security-releases/">
<p>Updates are now available for all active Node.js release lines. These include fixes for the vulnerabilities identified in the initial announcement. They also include upgrades of Node.js 6 and 8 to OpenSSL 1.0.2q, and upgrades of Node.js 10 and 11 to OpenSSL 1.1.0j.</p>
<p>We recommend that all Node.js users upgrade to a version listed below as soon as possible.</p>
<h1>Debugger port 5858 listens on any interface by default (CVE-2018-12120)</h1>
<p>All versions of Node.js 6 are vulnerable and the severity is HIGH. When the debugger is enabled with <code>node --debug</code> or <code>node debug</code>, it listens to port 5858 on all interfaces by default. This may allow remote computers to attach to the debug port and evaluate arbitrary JavaScript. The default interface is now localhost. It has always been possible to start the debugger on a specific interface, such as <code>node --debug=localhost</code>. The debugger was removed in Node.js 8 and replaced with the inspector, so no versions from 8 and later are vulnerable.</p>
<h1>Denial of Service with large HTTP headers (CVE-2018-12121)</h1>
<p>All versions of 6 and later are vulnerable and the severity is HIGH. By using a combination of many requests with maximum sized headers (almost 80 KB per connection), and carefully timed completion of the headers, it is possible to cause the HTTP server to abort from heap allocation failure. Attack potential is mitigated by the use of a load balancer or other proxy layer.</p>
<p>The total size of HTTP headers received by Node.js now must not exceed 8192 bytes.</p>
<h1>"Slowloris" HTTP Denial of Service (CVE-2018-12122)</h1>
<p>All versions of Node.js 6 and later are vulnerable and the severity is LOW. An attacker can cause a Denial of Service (DoS) by sending headers very slowly keeping HTTP or HTTPS connections and associated resources alive for a long period of time. Attack potential is mitigated by the use of a load balancer or other proxy layer.</p>
<p>A timeout of 40 seconds now applies to servers receiving HTTP headers. This value can be adjusted with <code>server.headersTimeout</code>. Where headers are not completely received within this period, the socket is destroyed on the next received chunk. In conjunction with <code>server.setTimeout()</code>, this aids in protecting against excessive resource retention and possible Denial of Service.</p>
<h1>Hostname spoofing in URL parser for javascript protocol (CVE-2018-12123)</h1>
<p>All versions of Node.js 6 and later are vulnerable and the severity is LOW. If a Node.js application is using <code>url.parse()</code> to determine the URL hostname, that hostname can be spoofed by using a mixed case "javascript:" (e.g. "javAscript:") protocol (other protocols are not affected). If security decisions are made about the URL based on the hostname, they may be incorrect.</p>
<h1>HTTP request splitting (CVE-2018-12116)</h1>
<p>Node.js 6 and 8 are vulnerable and the severity is MEDIUM. If Node.js can be convinced to use unsanitized user-provided Unicode data for the <code>path</code> option of an HTTP request, then data can be provided which will trigger a second, unexpected, and user-defined HTTP request to made to the same server.</p>
<h1>OpenSSL Timing vulnerability in ECDSA signature generation (CVE-2018-0735)</h1>
<p>The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side-channel attack. An attacker could use variations in the signing algorithm to recover the private key.</p>
<h1>OpenSSL Timing vulnerability in DSA signature generation (CVE-2018-0734)</h1>
<p>The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side-channel attack. An attacker could use variations in the signing algorithm to recover the private key.</p>
<h1>OpenSSL Microarchitecture timing vulnerability in ECC scalar multiplication (CVE-2018-5407)</h1>
<p>OpenSSL ECC scalar multiplication, used in e.g. ECDSA and ECDH, has been shown to be vulnerable to a microarchitecture timing side-channel attack. An attacker with sufficient access to mount local timing attacks during ECDSA signature generation could recover the private key.</p>
</blockquote>
</body>
</description>
<references>
<url>https://nodejs.org/en/blog/vulnerability/november-2018-security-releases/</url>
<cvename>CVE-2018-12120</cvename>
<cvename>CVE-2018-12121</cvename>
<cvename>CVE-2018-12122</cvename>
<cvename>CVE-2018-12123</cvename>
<cvename>CVE-2018-12116</cvename>
<cvename>CVE-2018-0735</cvename>
<cvename>CVE-2018-0734</cvename>
<cvename>CVE-2018-5407</cvename>
</references>
<dates>
<discovery>2018-11-27</discovery>
<entry>2018-12-10</entry>
</dates>
</vuln>
<vuln vid="f6d6308a-f2ec-11e8-b005-6805ca2fa271">
<topic>powerdns-recursor -- Crafted query can cause a denial of service</topic>
<affects>
<package>
<name>powerdns-recursor</name>
<range><lt>4.1.8</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>powerdns Team reports:</p>
<blockquote cite="https://doc.powerdns.com/recursor/changelog/4.1.html">
<p>CVE-2018-16855: An issue has been found in PowerDNS Recursor where a remote attacker sending a DNS query can trigger an out-of-bounds memory read while computing the hash of the query for a packet cache lookup, possibly leading to a crash. When the PowerDNS Recursor is run inside a supervisor like supervisord or systemd, a crash will lead to an automatic restart, limiting the impact to a somewhat degraded service.</p>
</blockquote>
</body>
</description>
<references>
<url>https://doc.powerdns.com/recursor/changelog/4.1.html</url>
<cvename>CVE-2018-16855</cvename>
</references>
<dates>
<discovery>2018-11-26</discovery>
<entry>2018-12-09</entry>
</dates>
</vuln>
<vuln vid="0e8f496a-b498-11e8-bdcf-74d435e60b7c">
<topic>py-asyncssh -- Allows bypass of authentication</topic>
<affects>
<package>
<name>py-asyncssh</name>
<range><lt>1.12.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>mitre.org Reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7749">
<p>The SSH server implementation of AsyncSSH before 1.12.1 does not properly check
whether authentication is completed before processing other requests
A customized SSH client can simply skip the authentication step.</p>
</blockquote>
</body>
</description>
<references>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7749</url>
</references>
<dates>
<discovery>2018-03-07</discovery>
<entry>2018-12-08</entry>
</dates>
</vuln>
<vuln vid="9d3428d4-f98c-11e8-a148-001b217b3468">
<topic>Gitlab -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>11.5.0</ge><lt>11.5.3</lt></range>
<range><ge>11.4.0</ge><lt>11.4.10</lt></range>
<range><ge>8.11.0</ge><lt>11.3.12</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/12/06/critical-security-release-gitlab-11-dot-5-dot-3-released">
<p>Directory Traversal in Templates API</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/12/06/critical-security-release-gitlab-11-dot-5-dot-3-released/</url>
<cvename>CVE-2018-19856</cvename>
</references>
<dates>
<discovery>2018-12-06</discovery>
<entry>2018-12-06</entry>
</dates>
</vuln>
<vuln vid="49cbe200-f92a-11e8-a89d-d43d7ef03aa6">
<topic>Flash Player -- multiple vulnerabilities</topic>
<affects>
<package>
<name>linux-flashplayer</name>
<range><lt>32.0.0.101</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Adobe reports:</p>
<blockquote cite="https://helpx.adobe.com/security/products/flash-player/apsb18-42.html">
<ul>
<li>This update resolves a use-after-free vulnerability that
could lead to arbitrary code execution (CVE-2018-15982).</li>
<li>This update resolves an insecure library loading vulnerability that
could lead to privilege escalation (CVE-2018-15983).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-15982</cvename>
<cvename>CVE-2018-15983</cvename>
<url>https://helpx.adobe.com/security/products/flash-player/apsb18-42.html</url>
</references>
<dates>
<discovery>2018-12-05</discovery>
<entry>2018-12-06</entry>
</dates>
</vuln>
<vuln vid="3aa27226-f86f-11e8-a085-3497f683cb16">
<topic>jenkins -- multiple vulnerabilities</topic>
<affects>
<package>
<name>jenkins</name>
<range><lt>2.154</lt></range>
</package>
<package>
<name>jenkins-lts</name>
<range><lt>2.138.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Jenkins Security Advisory:</p>
<blockquote cite="https://jenkins.io/security/advisory/2018-12-05/">
<h1>Description</h1>
<h5>(Critical) SECURITY-595</h5>
<p>Code execution through crafted URLs</p>
<h5>(Medium) SECURITY-904</h5>
<p>Forced migration of user records</p>
<h5>(Medium) SECURITY-1072</h5>
<p>Workspace browser allowed accessing files outside the workspace</p>
<h5>(Medium) SECURITY-1193</h5>
<p>Potential denial of service through cron expression form validation</p>
</blockquote>
</body>
</description>
<references>
<url>https://jenkins.io/security/advisory/2018-12-05/</url>
</references>
<dates>
<discovery>2018-12-05</discovery>
<entry>2018-12-05</entry>
</dates>
</vuln>
<vuln vid="889e35f4-f6a0-11e8-82dc-fcaa147e860e">
<topic>moodle -- Login CSRF vulnerability</topic>
<affects>
<package>
<name>moodle31</name>
<range><lt>3.1.15</lt></range>
</package>
<package>
<name>moodle33</name>
<range><lt>3.3.9</lt></range>
</package>
<package>
<name>moodle34</name>
<range><lt>3.4.6</lt></range>
</package>
<package>
<name>moodle35</name>
<range><lt>3.5.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>moodle reports:</p>
<blockquote cite="https://moodle.org/mod/forum/discuss.php?d=378731">
<p>The login form is not protected by a token to prevent login cross-site
request forgery.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-16854</cvename>
<url>https://moodle.org/mod/forum/discuss.php?d=378731</url>
</references>
<dates>
<discovery>2018-11-06</discovery>
<entry>2018-12-03</entry>
</dates>
</vuln>
<vuln vid="f96044a2-7df9-414b-9f6b-6e5b85d06c86">
<topic>Rails -- Active Job vulnerability</topic>
<affects>
<package>
<name>rubygem-activejob4</name>
<range><lt>4.2.11</lt></range>
</package>
<package>
<name>rubygem-activejob5</name>
<range><lt>5.1.6.1</lt></range>
</package>
<package>
<name>rubygem-activejob50</name>
<range><lt>5.0.7.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Ruby on Rails blog:</p>
<blockquote cite="https://weblog.rubyonrails.org/2018/11/27/Rails-4-2-5-0-5-1-5-2-have-been-released/">
<p>Rails 4.2.11, 5.0.7.1, 5.1.6.1 and 5.2.1.1 have been released! These
contain the following important security fixes, and it is recommended
that users upgrade as soon as possible</p>
<p>CVE-2018-16476 Broken Access Control vulnerability in Active Job:
Carefully crafted user input can cause Active Job to deserialize it
using GlobalId and allow an attacker to have access to information that
they should not have.</p>
</blockquote>
</body>
</description>
<references>
<url>https://weblog.rubyonrails.org/2018/11/27/Rails-4-2-5-0-5-1-5-2-have-been-released/</url>
<cvename>CVE-2018-16476</cvename>
</references>
<dates>
<discovery>2018-11-27</discovery>
<entry>2018-12-02</entry>
</dates>
</vuln>
<vuln vid="3563fae5-f60c-11e8-b513-5404a68ad561">
<topic>uriparser -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>uriparser</name>
<range><lt>0.9.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The upstream project reports:</p>
<blockquote cite="https://github.com/uriparser/uriparser/blob/uriparser-0.9.0/ChangeLog">
<p>* Fixed: Out-of-bounds write in uriComposeQuery* and uriComposeQueryEx*
Commit 864f5d4c127def386dd5cc926ad96934b297f04e
Thanks to Google Autofuzz team for the report!</p>
<p>* Fixed: Detect integer overflow in uriComposeQuery* and uriComposeQueryEx*
Commit f76275d4a91b28d687250525d3a0c5509bbd666f
Thanks to Google Autofuzz team for the report!</p>
<p>* Fixed: Protect uriResetUri* against acting on NULL input
Commit f58c25069cf4a986fe17a80c5b38687e31feb539</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-19198</cvename>
<cvename>CVE-2018-19199</cvename>
<cvename>CVE-2018-19200</cvename>
<url>https://github.com/uriparser/uriparser/blob/uriparser-0.9.0/ChangeLog</url>
</references>
<dates>
<discovery>2018-10-27</discovery>
<entry>2018-12-02</entry>
</dates>
</vuln>
<vuln vid="c7b1af20-f34f-11e8-9cde-e0d55e2a8bf9">
<topic>messagelib -- HTML email can open browser window automatically</topic>
<affects>
<package>
<name>messagelib</name>
<range><lt>18.08.3_2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Albert Astals Cid reports:</p>
<blockquote cite="https://www.kde.org/info/security/advisory-20181128-1.txt">
<p>messagelib is the library used by KMail to display emails.</p>
<p>messagelib by default displays emails as plain text, but gives the user
an option to "Prefer HTML to plain text" in the settings and if that option
is not enabled there is way to enable HTML display when an email contains HTML.</p>
<p>Some HTML emails can trick messagelib into opening a new browser window when
displaying said email as HTML.</p>
<p>This happens even if the option to allow the HTML emails to access
remote servers is disabled in KMail settings.</p>
<p>This means that the owners of the servers referred in the email can see
in their access logs your IP address.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-19516</cvename>
<url>https://www.kde.org/info/security/advisory-20181128-1.txt</url>
</references>
<dates>
<discovery>2018-11-28</discovery>
<entry>2018-11-28</entry>
</dates>
</vuln>
<vuln vid="93f8e0ff-f33d-11e8-be46-0019dbb15b3f">
<topic>payara -- Default typing issue in Jackson Databind</topic>
<affects>
<package>
<name>payara</name>
<range><eq>4.1.2.181.3</eq></range>
<range><eq>4.1.2.182</eq></range>
<range><eq>5.181.3</eq></range>
<range><eq>5.182</eq></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7489">
<p>FasterXML jackson-databind before 2.8.11.1 and 2.9.x before
2.9.5 allows unauthenticated remote code execution because of
an incomplete fix for the CVE-2017-7525 deserialization flaw.
This is exploitable by sending maliciously crafted JSON input
to the readValue method of the ObjectMapper, bypassing a
blacklist that is ineffective if the c3p0 libraries are
available in the classpath.</p>
</blockquote>
</body>
</description>
<references>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7489</url>
<cvename>CVE-2018-7489</cvename>
</references>
<dates>
<discovery>2018-02-26</discovery>
<entry>2018-11-28</entry>
</dates>
</vuln>
<vuln vid="22bc5327-f33f-11e8-be46-0019dbb15b3f">
<topic>payara -- Code execution via crafted PUT requests to JSPs</topic>
<affects>
<package>
<name>payara</name>
<range><eq>4.1.2.174</eq></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12615">
<p>When running Apache Tomcat 7.0.0 to 7.0.79 on Windows with HTTP
PUTs enabled (e.g. via setting the readonly initialisation
parameter of the Default to false) it was possible to upload a
JSP file to the server via a specially crafted request. This
JSP could then be requested and any code it contained would be
executed by the server.</p>
</blockquote>
</body>
</description>
<references>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12615</url>
<cvename>CVE-2017-12615</cvename>
</references>
<dates>
<discovery>2017-08-07</discovery>
<entry>2018-11-28</entry>
</dates>
</vuln>
<vuln vid="d70c9e18-f340-11e8-be46-0019dbb15b3f">
<topic>payara -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>payara</name>
<range><eq>4.1.2.173</eq></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<blockquote cite="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031">
<p>Apache Commons FileUpload before 1.3.3
DiskFileItem File Manipulation Remote Code Execution.</p>
</blockquote>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3239">
<p>Vulnerability in the Oracle GlassFish Server component of
Oracle Fusion Middleware (subcomponent: Administration).
Supported versions that are affected are 3.0.1 and 3.1.2.
Easily exploitable vulnerability allows low privileged attacker
with logon to the infrastructure where Oracle GlassFish Server
executes to compromise Oracle GlassFish Server. Successful
attacks of this vulnerability can result in unauthorized read
access to a subset of Oracle GlassFish Server accessible data.
CVSS v3.0 Base Score 3.3 (Confidentiality impacts).</p>
</blockquote>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3247">
<p>Vulnerability in the Oracle GlassFish Server component of Oracle
Fusion Middleware (subcomponent: Core). Supported versions that
are affected are 2.1.1, 3.0.1 and 3.1.2. Easily exploitable
vulnerability allows unauthenticated attacker with network access
via SMTP to compromise Oracle GlassFish Server. Successful
attacks require human interaction from a person other than the
attacker. Successful attacks of this vulnerability can result in
unauthorized update, insert or delete access to some of Oracle
GlassFish Server accessible data. CVSS v3.0 Base Score 4.3
(Integrity impacts).</p>
</blockquote>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3249">
<p>Vulnerability in the Oracle GlassFish Server component of
Oracle Fusion Middleware (subcomponent: Security). Supported
versions that are affected are 2.1.1, 3.0.1 and 3.1.2.
Easily exploitable vulnerability allows unauthenticated attacker
with network access via LDAP to compromise Oracle GlassFish Server.
Successful attacks of this vulnerability can result in unauthorized
update, insert or delete access to some of Oracle GlassFish Server
accessible data as well as unauthorized read access to a subset of
Oracle GlassFish Server accessible data and unauthorized ability
to cause a partial denial of service (partial DOS) of Oracle
GlassFish Server. CVSS v3.0 Base Score 7.3 (Confidentiality,
Integrity and Availability impacts).</p>
</blockquote>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3250">
<p>Vulnerability in the Oracle GlassFish Server component of Oracle
Fusion Middleware (subcomponent: Security). Supported versions that
are affected are 2.1.1, 3.0.1 and 3.1.2. Easily exploitable
vulnerability allows unauthenticated attacker with network access
via HTTP to compromise Oracle GlassFish Server. Successful attacks
of this vulnerability can result in unauthorized update, insert or
delete access to some of Oracle GlassFish Server accessible data as
well as unauthorized read access to a subset of Oracle GlassFish
Server accessible data and unauthorized ability to cause a partial
denial of service (partial DOS) of Oracle GlassFish Server.
CVSS v3.0 Base Score 7.3 (Confidentiality, Integrity and
Availability impacts).</p>
</blockquote>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5528">
<p>Vulnerability in the Oracle GlassFish Server component of Oracle
Fusion Middleware (subcomponent: Security). Supported versions that
are affected are 2.1.1, 3.0.1 and 3.1.2. Difficult to exploit
vulnerability allows unauthenticated attacker with network access
via multiple protocols to compromise Oracle GlassFish Server. While
the vulnerability is in Oracle GlassFish Server, attacks may
significantly impact additional products. Successful attacks of this
vulnerability can result in takeover of Oracle GlassFish Server.
CVSS v3.0 Base Score 9.0 (Confidentiality, Integrity and
Availability impacts).</p>
</blockquote>
</body>
</description>
<references>
<url>http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031</url>
<cvename>CVE-2016-1000031</cvename>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3239</url>
<cvename>CVE-2017-3239</cvename>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3247</url>
<cvename>CVE-2017-3247</cvename>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3249</url>
<cvename>CVE-2017-3249</cvename>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3250</url>
<cvename>CVE-2017-3250</cvename>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5528</url>
<cvename>CVE-2016-5528</cvename>
</references>
<dates>
<discovery>2016-06-16</discovery>
<entry>2018-11-28</entry>
</dates>
</vuln>
<vuln vid="8a4aba2d-f33e-11e8-9416-001b217b3468">
<topic>Gitlab -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>11.5.0</ge><lt>11.5.1</lt></range>
<range><ge>11.4.0</ge><lt>11.4.8</lt></range>
<range><ge>0</ge><lt>11.3.11</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/11/28/security-release-gitlab-11-dot-5-dot-1-released">
<p>View Names of Private Groups</p>
<p>Persistent XSS in Environments</p>
<p>SSRF in Prometheus integration</p>
<p>Unauthorized Promotion of Milestones</p>
<p>Exposure of Confidential Issue Title</p>
<p>Persisent XSS in Markdown Fields via Mermaid Script</p>
<p>Persistent XSS in Markdown Fields via Unrecognized HTML Tags</p>
<p>Symlink Race Condition in Pages</p>
<p>Unauthorized Changes by Guest User in Issues</p>
<p>Unauthorized Comments on Locked Issues</p>
<p>Improper Enforcement of Token Scope</p>
<p>CRLF Injection in Project Mirroring</p>
<p>XSS in OAuth Authorization</p>
<p>SSRF in Webhooks</p>
<p>Send Email on Email Address Change</p>
<p>Workhorse Logs Contained Tokens</p>
<p>Unauthorized Publishing of Draft Comments</p>
<p>Guest Can Set Weight of a New Issue</p>
<p>Disclosure of Private Group's Members and Milestones</p>
<p>Persisent XSS in Operations</p>
<p>Reporter Can View Operations Page</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/11/28/security-release-gitlab-11-dot-5-dot-1-released/</url>
<cvename>CVE-2018-19494</cvename>
<cvename>CVE-2018-19493</cvename>
<cvename>CVE-2018-19495</cvename>
<cvename>CVE-2018-19496</cvename>
<cvename>CVE-2018-19577</cvename>
<cvename>CVE-2018-19573</cvename>
<cvename>CVE-2018-19570</cvename>
<cvename>CVE-2018-19572</cvename>
<cvename>CVE-2018-19576</cvename>
<cvename>CVE-2018-19575</cvename>
<cvename>CVE-2018-19569</cvename>
<cvename>CVE-2018-19585</cvename>
<cvename>CVE-2018-19574</cvename>
<cvename>CVE-2018-19571</cvename>
<cvename>CVE-2018-19580</cvename>
<cvename>CVE-2018-19583</cvename>
<cvename>CVE-2018-19582</cvename>
<cvename>CVE-2018-19581</cvename>
<cvename>CVE-2018-19584</cvename>
<cvename>CVE-2018-19579</cvename>
<cvename>CVE-2018-19578</cvename>
</references>
<dates>
<discovery>2018-11-28</discovery>
<entry>2018-11-28</entry>
</dates>
</vuln>
<vuln vid="54976998-f248-11e8-81e2-005056a311d1">
<topic>samba -- multiple vulnerabilities</topic>
<affects>
<package>
<name>samba46</name>
<range><le>4.6.16</le></range>
</package>
<package>
<name>samba47</name>
<range><lt>4.7.12</lt></range>
</package>
<package>
<name>samba48</name>
<range><lt>4.8.7</lt></range>
</package>
<package>
<name>samba49</name>
<range><lt>4.9.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The samba project reports:</p>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-14629.html">
<p>All versions of Samba from 4.0.0 onwards are vulnerable to infinite
query recursion caused by CNAME loops. Any dns record can be added via
ldap by an unprivileged user using the ldbadd tool, so this is a
security issue.</p>
</blockquote>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-16841.html">
<p>When configured to accept smart-card authentication, Samba's KDC will call
talloc_free() twice on the same memory if the principal in a validly signed
certificate does not match the principal in the AS-REQ.</p>
</blockquote>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-16851.html">
<p>During the processing of an LDAP search before Samba's AD DC returns
the LDAP entries to the client, the entries are cached in a single
memory object with a maximum size of 256MB. When this size is
reached, the Samba process providing the LDAP service will follow the
NULL pointer, terminating the process.</p>
</blockquote>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-16852.html">
<p>During the processing of an DNS zone in the DNS management DCE/RPC server,
the internal DNS server or the Samba DLZ plugin for BIND9, if the
DSPROPERTY_ZONE_MASTER_SERVERS property or DSPROPERTY_ZONE_SCAVENGING_SERVERS
property is set, the server will follow a NULL pointer and terminate</p>
</blockquote>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-16853.html">
<p>A user in a Samba AD domain can crash the KDC when Samba is built in the
non-default MIT Kerberos configuration.</p>
</blockquote>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-16857.html">
<p>AD DC Configurations watching for bad passwords (to restrict brute forcing
of passwords) in a window of more than 3 minutes may not watch for bad
passwords at all.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.samba.org/samba/security/CVE-2018-14629.html</url>
<cvename>CVE-2018-14629</cvename>
<url>https://www.samba.org/samba/security/CVE-2018-16841.html</url>
<cvename>CVE-2018-16841</cvename>
<url>https://www.samba.org/samba/security/CVE-2018-16851.html</url>
<cvename>CVE-2018-16851</cvename>
<url>https://www.samba.org/samba/security/CVE-2018-16852.html</url>
<cvename>CVE-2018-16852</cvename>
<url>https://www.samba.org/samba/security/CVE-2018-16853.html</url>
<cvename>CVE-2018-16853</cvename>
<url>https://www.samba.org/samba/security/CVE-2018-16857.html</url>
<cvename>CVE-2018-16857</cvename>
</references>
<dates>
<discovery>2018-08-14</discovery>
<entry>2018-08-14</entry>
</dates>
</vuln>
<vuln vid="ec49f6b5-ee39-11e8-b2f4-74d435b63d51">
<topic>php-imap -- imap_open allows to run arbitrary shell commands via mailbox parameter</topic>
<affects>
<package>
<name>php56-imap</name>
<range><lt>5.6.38_1</lt></range>
</package>
<package>
<name>php70-imap</name>
<range><lt>*</lt></range>
</package>
<package>
<name>php71-imap</name>
<range><lt>*</lt></range>
</package>
<package>
<name>php72-imap</name>
<range><lt>*</lt></range>
</package>
<package>
<name>php73-imap</name>
<range><lt>*</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The PHP team reports:</p>
<blockquote cite="https://bugs.php.net/bug.php?id=77153">
<p>imap_open allows to run arbitrary shell commands via mailbox parameter.</p>
</blockquote>
</body>
</description>
<references>
<url>https://bugs.php.net/bug.php?id=77153</url>
</references>
<dates>
<discovery>2018-10-23</discovery>
<entry>2018-11-22</entry>
<modified>2018-11-22</modified>
</dates>
</vuln>
<vuln vid="b036faba-edd8-11e8-b3b7-00e04c1ea73d">
<topic>phpmailer -- Multiple vulnerability</topic>
<affects>
<package>
<name>phpmailer</name>
<range><lt>5.2.27</lt></range>
</package>
<package>
<name>phpmailer6</name>
<range><lt>6.0.6</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>SO-AND-SO reports:</p>
<blockquote cite="https://github.com/PHPMailer/PHPMailer/releases/tag/v6.0.6">
<p>CVE-2018-19296:Fix potential object injection vulnerability.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/PHPMailer/PHPMailer/releases/tag/v5.2.27</url>
<url>https://github.com/PHPMailer/PHPMailer/releases/tag/v6.0.6</url>
<cvename>CVE-2018-19296</cvename>
</references>
<dates>
<discovery>2018-11-16</discovery>
<entry>2018-11-21</entry>
<modified>2018-11-23</modified>
</dates>
</vuln>
<vuln vid="8f128c72-ecf9-11e8-aa00-6451062f0f7a">
<topic>Flash Player -- arbitrary code execution</topic>
<affects>
<package>
<name>linux-flashplayer</name>
<range><lt>31.0.0.153</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Adobe reports:</p>
<blockquote cite="https://helpx.adobe.com/security/products/flash-player/apsb18-44.html">
<ul>
<li>This update resolves a type confusion vulnerability that
could lead to arbitrary code execution (CVE-2018-15981).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-15981</cvename>
<url>https://helpx.adobe.com/security/products/flash-player/apsb18-44.html</url>
</references>
<dates>
<discovery>2018-11-20</discovery>
<entry>2018-11-20</entry>
</dates>
</vuln>
<vuln vid="d889d32c-ecd9-11e8-9416-001b217b3468">
<topic>Gitlab -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>11.4.0</ge><lt>11.4.6</lt></range>
<range><ge>8.9.0</ge><lt>11.3.10</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/11/19/critical-security-release-gitlab-11-dot-4-dot-6-released/">
<p>Persistent XSS Autocompletion</p>
<p>Unauthorized service template creation</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/11/19/critical-security-release-gitlab-11-dot-4-dot-6-released/</url>
<cvename>CVE-2018-18643</cvename>
<cvename>CVE-2018-19359</cvename>
</references>
<dates>
<discovery>2018-11-19</discovery>
<entry>2018-11-20</entry>
</dates>
</vuln>
<vuln vid="0aee2f13-ec1d-11e8-8c92-6805ca2fa271">
<topic>powerdns -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>powerdns</name>
<range><lt>4.1.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>PowerDNS Team reports:</p>
<blockquote cite="https://doc.powerdns.com/authoritative/changelog/4.1.html">
<p>CVE-2018-10851: An issue has been found in PowerDNS Authoritative Server allowing
an authorized user to cause a memory leak by inserting a specially crafted record
in a zone under their control, then sending a DNS query for that record. The issue
is due to the fact that some memory is allocated before the parsing and is not
always properly released if the record is malformed. When the PowerDNS
Authoritative Server is run inside the guardian (--guardian), or inside a
supervisor like supervisord or systemd, an out-of-memory crash will lead to an
automatic restart, limiting the impact to a somewhat degraded service.</p>
<p>CVE-2018-14626: An issue has been found in PowerDNS Authoritative Server allowing
a remote user to craft a DNS query that will cause an answer without DNSSEC
records to be inserted into the packet cache and be returned to clients asking for
DNSSEC records, thus hiding the presence of DNSSEC signatures for a specific qname
and qtype. For a DNSSEC-signed domain, this means that DNSSEC validating clients
will consider the answer to be bogus until it expires from the packet cache,
leading to a denial of service.</p>
</blockquote>
</body>
</description>
<references>
<url>https://doc.powerdns.com/authoritative/changelog/4.1.html</url>
<cvename>CVE-2018-10851</cvename>
<cvename>CVE-2018-14626</cvename>
</references>
<dates>
<discovery>2018-11-06</discovery>
<entry>2018-11-19</entry>
</dates>
</vuln>
<vuln vid="e9aa0e4c-ea8b-11e8-a5b7-00e04c1ea73d">
<topic>powerdns-recursor -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>powerdns-recursor</name>
<range><lt>4.1.7</lt></range>
</package>
<package>
<name>powerdns-recursor40</name>
<range><lt>4.0.9</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>powerdns Team reports:</p>
<blockquote cite="https://doc.powerdns.com/recursor/changelog/4.1.html">
<p>CVE-2018-10851: An issue has been found in PowerDNS Recursor allowing
a malicious authoritative server to cause a memory leak by sending specially
crafted records. The issue is due to the fact that some memory is allocated
before the parsing and is not always properly released if the record is malformed.
When the PowerDNS Recursor is run inside a supervisor like supervisord or systemd,
an out-of-memory crash will lead to an automatic restart, limiting the impact to
a somewhat degraded service.</p>
<p>CVE-2018-14626: An issue has been found in PowerDNS Recursor allowing a remote
user to craft a DNS query that will cause an answer without DNSSEC records to be
inserted into the packet cache and be returned to clients asking for DNSSEC
records, thus hiding the presence of DNSSEC signatures for a specific qname and
qtype. For a DNSSEC-signed domain, this means that clients performing DNSSEC
validation by themselves might consider the answer to be bogus until it expires
from the packet cache, leading to a denial of service.</p>
<p>CVE-2018-14644: An issue has been found in PowerDNS Recursor where a remote attacker
sending a DNS query for a meta-type like OPT can lead to a zone being wrongly cached
as failing DNSSEC validation. It only arises if the parent zone is signed, and all
the authoritative servers for that parent zone answer with FORMERR to a query for at
least one of the meta-types. As a result, subsequent queries from clients requesting
DNSSEC validation will be answered with a ServFail.</p>
</blockquote>
</body>
</description>
<references>
<url>https://doc.powerdns.com/recursor/changelog/4.1.html</url>
<cvename>CVE-2018-10851</cvename>
<cvename>CVE-2018-14626</cvename>
<cvename>CVE-2018-14644</cvename>
</references>
<dates>
<discovery>2018-11-06</discovery>
<entry>2018-11-17</entry>
<modified>2018-11-19</modified>
</dates>
</vuln>
<vuln vid="c6fb2734-e835-11e8-b14b-001999f8d30b">
<topic>asterisk -- Remote crash vulnerability DNS SRV and NAPTR lookups</topic>
<affects>
<package>
<name>asterisk15</name>
<range><lt>15.6.1</lt></range>
</package>
<package>
<name>asterisk16</name>
<range><lt>16.0.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Asterisk project reports:</p>
<blockquote cite="http://www.asterisk.org/downloads/security-advisories">
<p>There is a buffer overflow vulnerability in dns_srv
and dns_naptr functions of Asterisk that allows an attacker
to crash Asterisk via a specially crafted DNS SRV or NAPTR
response. The attackers request causes Asterisk to segfault
and crash.</p>
</blockquote>
</body>
</description>
<references>
<url>https://downloads.asterisk.org/pub/security/AST-2018-010.html</url>
</references>
<dates>
<discovery>2018-10-23</discovery>
<entry>2018-11-14</entry>
</dates>
</vuln>
<vuln vid="b69292e8-e798-11e8-ae07-6451062f0f7a">
<topic>Flash Player -- information disclosure</topic>
<affects>
<package>
<name>linux-flashplayer</name>
<range><lt>31.0.0.148</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Adobe reports:</p>
<blockquote cite="https://helpx.adobe.com/security/products/flash-player/apsb18-39.html">
<ul>
<li>This update resolves a out-of-bounds vulnerability that
could lead to information disclosure (CVE-2018-15978).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-15978</cvename>
<url>https://helpx.adobe.com/security/products/flash-player/apsb18-39.html</url>
</references>
<dates>
<discovery>2018-11-13</discovery>
<entry>2018-11-13</entry>
</dates>
</vuln>
<vuln vid="6f170cf2-e6b7-11e8-a9a8-b499baebfeaf">
<topic>OpenSSL -- timing vulnerability</topic>
<affects>
<package>
<name>openssl</name>
<range><lt>1.0.2p_2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The OpenSSL project reports:</p>
<blockquote cite="https://www.openssl.org/news/secadv/20181112.txt">
<p>Microarchitecture timing vulnerability in ECC scalar
multiplication. Severity: Low<br/>
OpenSSL ECC scalar multiplication, used in e.g. ECDSA and ECDH, has
been shown to be vulnerable to a microarchitecture timing side channel
attack. An attacker with sufficient access to mount local timing
attacks during ECDSA signature generation could recover the private
key.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.openssl.org/news/secadv/20181112.txt</url>
<cvename>CVE-2018-5407</cvename>
</references>
<dates>
<discovery>2018-11-12</discovery>
<entry>2018-11-12</entry>
</dates>
</vuln>
<vuln vid="1460aa25-e6ab-11e8-a733-e0d55e2a8bf9">
<topic>kio-extras -- HTML Thumbnailer automatic remote file access</topic>
<affects>
<package>
<name>kio-extras</name>
<range><lt>18.08.3_2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Albert Astals Cid reports:</p>
<blockquote cite="https://www.kde.org/info/security/advisory-20181012-1.txt">
<p>Various KDE applications share a plugin system to create thumbnails
of various file types for displaying in file managers, file dialogs, etc.
kio-extras contains a thumbnailer plugin for HTML files.
</p>
<p>
The HTML thumbnailer was incorrectly accessing some content of
remote URLs listed in HTML files. This meant that the owners of the servers
referred in HTML files in your system could have seen in their access logs
your IP address every time the thumbnailer tried to create the thumbnail.
</p>
<p>
The HTML thumbnailer has been removed in upcoming KDE Applications 18.12.0
because it was actually not creating thumbnails for files at all.
</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-19120</cvename>
<url>https://www.kde.org/info/security/advisory-20181012-1.txt</url>
</references>
<dates>
<discovery>2018-11-12</discovery>
<entry>2018-11-12</entry>
</dates>
</vuln>
<vuln vid="791841a3-d484-4878-8909-92ef9ce424f4">
<topic>patch -- multiple vulnerabilities</topic>
<affects>
<package>
<name>patch</name>
<range><lt>2.7.6_1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>NVD reports:</p>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2018-6951">
<p>An issue was discovered in GNU patch through 2.7.6. There is a segmentation fault, associated with a NULL pointer dereference, leading to a denial of service in the intuit_diff_type function in pch.c, aka a "mangled rename" issue.</p>
</blockquote>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2018-6952">
<p>A double free exists in the another_hunk function in pch.c in GNU patch through 2.7.6.</p>
</blockquote>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2018-1000156">
<p>GNU Patch version 2.7.6 contains an input validation vulnerability when processing patch files, specifically the EDITOR_PROGRAM invocation (using ed) can result in code execution. This attack appear to be exploitable via a patch file processed via the patch utility. This is similar to FreeBSD's CVE-2015-1418 however although they share a common ancestry the code bases have diverged over time.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-6951</cvename>
<cvename>CVE-2018-6952</cvename>
<cvename>CVE-2018-1000156</cvename>
<url>https://savannah.gnu.org/bugs/?53132</url>
<url>https://savannah.gnu.org/bugs/?53133</url>
<url>https://savannah.gnu.org/bugs/?53566</url>
</references>
<dates>
<discovery>2018-04-16</discovery>
<entry>2018-11-11</entry>
<modified>2018-11-11</modified>
</dates>
</vuln>
<vuln vid="92a6efd0-e40d-11e8-ada4-408d5cf35399">
<topic>lighttpd - use-after-free vulnerabilities</topic>
<affects>
<package>
<name>lighttpd</name>
<range><lt>1.4.51</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Lighttpd Project reports:</p>
<blockquote cite="https://www.lighttpd.net/2018/10/14/1.4.51/">
<p>Security fixes for Lighttpd:</p>
<ul>
<li><p>security: process headers after combining folded headers</p></li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://www.lighttpd.net/2018/10/14/1.4.51/</url>
<freebsdpr>ports/232278</freebsdpr>
</references>
<dates>
<discovery>2018-08-26</discovery>
<entry>2018-11-09</entry>
</dates>
</vuln>
<vuln vid="1c27a706-e3aa-11e8-b77a-6cc21735f730">
<topic>PostgreSQL -- SQL injection in pg_upgrade and pg_dump</topic>
<affects>
<package>
<name>postgresql10-server</name>
<range><lt>10.6</lt></range>
</package>
<package>
<name>postgresql96-server</name>
<range><lt>9.6.11</lt></range>
</package>
<package>
<name>postgresql95-server</name>
<range><lt>9.5.15</lt></range>
</package>
<package>
<name>postgresql94-server</name>
<range><lt>9.4.20</lt></range>
</package>
<package>
<name>postgresql93-server</name>
<range><lt>9.3.25</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The PostgreSQL project reports:</p>
<blockquote cite="https://www.postgresql.org/about/news/1878/">
<p>CVE-2018-16850: SQL injection in pg_upgrade and pg_dump,
via CREATE TRIGGER ... REFERENCING.</p>
<p>Using a purpose-crafted trigger definition, an attacker can run
arbitrary SQL statements with superuser privileges when a superuser
runs pg_upgrade on the database or during a pg_dump dump/restore
cycle. This attack requires a CREATE privilege on some non-temporary
schema or a TRIGGER privilege on a table. This is exploitable in the
default PostgreSQL configuration, where all users have CREATE
privilege on public schema.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.postgresql.org/about/news/1905/</url>
<cvename>CVE-2018-16850</cvename>
</references>
<dates>
<discovery>2018-11-08</discovery>
<entry>2018-11-08</entry>
</dates>
</vuln>
<vuln vid="84ca56be-e1de-11e8-bcfd-00e04c1ea73d">
<topic>NGINX -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>nginx</name>
<range><lt>1.14.1</lt></range>
</package>
<package>
<name>nginx-devel</name>
<range><lt>1.15.6</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>NGINX Team reports:</p>
<blockquote cite="http://nginx.org/en/security_advisories.html">
<p>Two security issues were identified in nginx HTTP/2 implementation,
which might cause excessive memory consumption (CVE-2018-16843)
and CPU usage (CVE-2018-16844).</p>
<p>The issues affect nginx compiled with the ngx_http_v2_module (not
compiled by default) if the "http2" option of the "listen" directive is
used in a configuration file.</p>
<p>A security issue was identified in the ngx_http_mp4_module, which might
allow an attacker to cause infinite loop in a worker process, cause a
worker process crash, or might result in worker process memory
isclosure by using a specially crafted mp4 file (CVE-2018-16845).</p>
<p>The issue only affects nginx if it is built with the ngx_http_mp4_module
(the module is not built by default) and the "mp4" directive is used in
the configuration file. Further, the attack is only possible if an
attacker is able to trigger processing of a specially crafted mp4 file
with the ngx_http_mp4_module. </p>
</blockquote>
</body>
</description>
<references>
<url>http://nginx.org/en/security_advisories.html</url>
<cvename>CVE-2018-16843</cvename>
<cvename>CVE-2018-16844</cvename>
<cvename>CVE-2018-16845</cvename>
</references>
<dates>
<discovery>2018-11-06</discovery>
<entry>2018-11-06</entry>
</dates>
</vuln>
<vuln vid="deb4f633-de1d-11e8-a9fb-080027f43a02">
<topic>gitea -- remote code exeution</topic>
<affects>
<package>
<name>gitea</name>
<range><lt>1.5.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Gitea project reports:</p>
<blockquote cite="https://blog.gitea.io/2018/10/gitea-1.5.3-is-released/">
<p>[This release] contains crit[i]cal security fix for vulnerability
that could potentially allow for authorized users to do remote code
ex[e]cution.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/go-gitea/gitea/pull/5177</url>
<url>https://github.com/go-gitea/gitea/pull/5196</url>
<url>https://github.com/go-macaron/session/commit/084f1e5c1071f585902a7552b483cee04bc00a14</url>
</references>
<dates>
<discovery>2018-10-25</discovery>
<entry>2018-11-01</entry>
</dates>
</vuln>
<vuln vid="e0ab1773-07c1-46c6-9170-4c5e81c00927">
<topic>curl -- multiple vulnerabilities</topic>
<affects>
<package>
<name>curl</name>
<range><ge>7.14.1</ge><lt>7.60.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>curl security problems:</p>
<blockquote cite="https://curl.haxx.se/docs/security.html">
<p>CVE-2018-16839: SASL password overflow via integer overflow</p>
<p>libcurl contains a buffer overrun in the SASL authentication code.</p>
<p>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.</p>
<p>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.</p>
<p>This bug is very similar to CVE-2017-14618.</p>
<p>It affects curl 7.33.0 to 7.61.1.</p>
<p>CVE-2018-16840: use-after-free in handle close</p>
<p>libcurl contains a heap use-after-free flaw in code related to closing
an easy handle.</p>
<p>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.</p>
<p>It affects curl 7.59.0 to 7.61.1.</p>
<p>CVE-2018-16842: warning message out-of-buffer read</p>
<p>curl contains a heap out of buffer read vulnerability.</p>
<p>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.</p>
<p>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.</p>
<p>This vulnerability could lead to a security issue if used in this or
similar situations:</p>
<p>1. a server somewhere uses the curl command line to run something</p>
<p>2. if it fails, it shows stderr to the user</p>
<p>3. the server takes user input for parts of its command line input</p>
<p>4. user provides something overly long that triggers this crash</p>
<p>5. the stderr output may now contain user memory contents that wasn't
meant to be available</p>
<p>It affects curl 7.14.1 to 7.61.1.</p>
</blockquote>
</body>
</description>
<references>
<url>https://curl.haxx.se/docs/security.html</url>
<url>https://curl.haxx.se/docs/CVE-2018-16839.html</url>
<url>https://curl.haxx.se/docs/CVE-2018-16840.html</url>
<url>https://curl.haxx.se/docs/CVE-2018-16842.html</url>
<cvename>CVE-2018-16839</cvename>
<cvename>CVE-2018-16840</cvename>
<cvename>CVE-2018-16842</cvename>
</references>
<dates>
<discovery>2018-10-31</discovery>
<entry>2018-11-01</entry>
</dates>
</vuln>
<vuln vid="b51d9e83-de08-11e8-9416-001b217b3468">
<topic>Gitlab -- SSRF in Kubernetes integration</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>11.4.0</ge><lt>11.4.4</lt></range>
<range><ge>11.3.0</ge><lt>11.3.9</lt></range>
<range><ge>11.0.0</ge><lt>11.2.8</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>SO-AND-SO reports:</p>
<blockquote cite="https://about.gitlab.com/2018/11/01/critical-security-release-gitlab-11-dot-4-dot-4-released/">
<p>SSRF in Kubernetes integration</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/11/01/critical-security-release-gitlab-11-dot-4-dot-4-released/</url>
<cvename>CVE-2018-18843</cvename>
</references>
<dates>
<discovery>2018-11-01</discovery>
<entry>2018-11-01</entry>
</dates>
</vuln>
<vuln vid="36a2a89e-7ee1-4ea4-ae22-7ca38019c8d0">
<topic>Loofah -- XSS vulnerability</topic>
<affects>
<package>
<name>rubygem-loofah</name>
<range><lt>2.2.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GitHub issue:</p>
<blockquote cite="https://github.com/flavorjones/loofah/issues/154">
<p>This issue has been created for public disclosure of an XSS
vulnerability that was responsibly reported (independently) by Shubham
Pathak and @yasinS (Yasin Soliman).</p>
<p>In the Loofah gem, through v2.2.2, unsanitized JavaScript may occur in
sanitized output when a crafted SVG element is republished.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/flavorjones/loofah/releases</url>
<url>https://github.com/flavorjones/loofah/issues/154</url>
<cvename>CVE-2018-16468</cvename>
</references>
<dates>
<discovery>2018-10-30</discovery>
<entry>2018-11-01</entry>
</dates>
</vuln>
<vuln vid="b9591212-dba7-11e8-9416-001b217b3468">
<topic>Gitlab -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>11.4.0</ge><lt>11.4.3</lt></range>
<range><ge>11.3.0</ge><lt>11.3.8</lt></range>
<range><ge>5.3.0</ge><lt>11.2.7</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/10/29/security-release-gitlab-11-dot-4-dot-3-released/">
<p>RCE in Gitlab Wiki API</p>
<p>SSRF in Hipchat integration</p>
<p>Cleartext storage of personal access tokens</p>
<p>Information exposure through stack trace error message</p>
<p>Persistent XSS autocomplete</p>
<p>Information exposure in stored browser history</p>
<p>Information exposure when replying to issues through email</p>
<p>Persistent XSS in License Management and Security Reports</p>
<p>Metrics information disclosure in Prometheus integration</p>
<p>Unauthorized changes to a protected branch's access levels</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/10/29/security-release-gitlab-11-dot-4-dot-3-released/</url>
<cvename>CVE-2018-18649</cvename>
<cvename>CVE-2018-18646</cvename>
<cvename>CVE-2018-18641</cvename>
<cvename>CVE-2018-18648</cvename>
<cvename>CVE-2018-18643</cvename>
<cvename>CVE-2018-18640</cvename>
<cvename>CVE-2018-18645</cvename>
<cvename>CVE-2018-18642</cvename>
<cvename>CVE-2018-18644</cvename>
<cvename>CVE-2018-18647</cvename>
</references>
<dates>
<discovery>2018-10-29</discovery>
<entry>2018-10-29</entry>
</dates>
</vuln>
<vuln vid="238ae7de-dba2-11e8-b713-b499baebfeaf">
<topic>OpenSSL -- Multiple vulnerabilities in 1.1 branch</topic>
<affects>
<package>
<name>openssl-devel</name>
<range><lt>1.1.0i_1</lt></range>
</package>
<package>
<name>openssl111</name>
<range><lt>1.1.1_2</lt></range>
</package>
<package>
<name>libressl</name>
<range><ge>2.8.0</ge><lt>2.8.3</lt></range>
</package>
<package>
<name>libressl-devel</name>
<range><ge>2.8.0</ge><lt>2.8.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The OpenSSL project reports:</p>
<blockquote cite="https://www.openssl.org/news/secadv/20181029.txt">
<p>Timing vulnerability in ECDSA signature generation
(CVE-2018-0735): The OpenSSL ECDSA signature algorithm has been
shown to be vulnerable to a timing side channel attack. An
attacker could use variations in the signing algorithm to
recover the private key (Low).</p>
<p>Timing vulnerability in DSA signature generation (CVE-2018-0734):
Avoid a timing attack that leaks information via a side channel
that triggers when a BN is resized. Increasing the size of the
BNs prior to doing anything with them suppresses the attack (Low).
</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.openssl.org/news/secadv/20181029.txt</url>
<url>https://github.com/openssl/openssl/commit/8abfe72e</url>
<cvename>CVE-2018-0735</cvename>
<cvename>CVE-2018-0734</cvename>
</references>
<dates>
<discovery>2018-10-29</discovery>
<entry>2018-10-29</entry>
<modified>2018-11-10</modified>
</dates>
</vuln>
<vuln vid="fa194483-dabd-11e8-bf39-5404a68ad561">
<topic>liveMedia -- potential remote code execution</topic>
<affects>
<package>
<name>liveMedia</name>
<range><lt>2018.10.17,2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Talos reports:</p>
<blockquote cite="https://talosintelligence.com/vulnerability_reports/TALOS-2018-0684">
<p>An exploitable code execution vulnerability exists in the HTTP packet-parsing functionality
of the LIVE555 RTSP server library. A specially crafted packet can cause a stack-based buffer
overflow, resulting in code execution. An attacker can send a packet to trigger this vulnerability.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-4013</cvename>
<url>https://talosintelligence.com/vulnerability_reports/TALOS-2018-0684</url>
<url>http://lists.live555.com/pipermail/live-devel/2018-October/021071.html</url>
</references>
<dates>
<discovery>2018-10-18</discovery>
<entry>2018-10-28</entry>
</dates>
</vuln>
<vuln vid="33c384f3-5af6-4662-9741-0acb21c7e499">
<topic>mini_httpd -- disclose arbitrary files is some circumstances</topic>
<affects>
<package>
<name>mini_httpd</name>
<range><lt>1.30</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Jef Poskanzer reports:</p>
<blockquote cite="http://acme.com/updates/archive/211.html">
<p>Prior versions allowed remote users to read arbitrary files in some circumstances.</p>
</blockquote>
</body>
</description>
<references>
<url>http://acme.com/updates/archive/211.html</url>
</references>
<dates>
<discovery>2018-10-26</discovery>
<entry>2018-10-26</entry>
</dates>
</vuln>
<vuln vid="4f7c6af3-6a2c-4ead-8453-04e509688d45">
<topic>salt -- multiple vulnerabilities</topic>
<affects>
<package>
<name>py27-salt</name>
<name>py32-salt</name>
<name>py33-salt</name>
<name>py34-salt</name>
<name>py35-salt</name>
<name>py36-salt</name>
<name>py37-salt</name>
<range><lt>2017.7.8</lt></range>
<range><ge>2018.3.0</ge><lt>2018.3.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>SaltStack reports:</p>
<blockquote cite="https://docs.saltstack.com/en/latest/topics/releases/2018.3.3.html">
<p>Remote command execution and incorrect access control when using
salt-api.</p>
<p>Directory traversal vulnerability when using salt-api. Allows an
attacker to determine what files exist on a server when querying
/run or /events.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-15751</cvename>
<cvename>CVE-2018-15750</cvename>
<url>https://docs.saltstack.com/en/latest/topics/releases/2018.3.3.html</url>
<url>https://docs.saltstack.com/en/2017.7/topics/releases/2017.7.8.html</url>
</references>
<dates>
<discovery>2018-10-24</discovery>
<entry>2018-10-27</entry>
</dates>
</vuln>
<vuln vid="7c3a02b9-3273-4426-a0ba-f90fad2ff72e">
<topic>mozilla -- multiple vulnerabilities</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>63.0_1,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.2.5</lt></range>
</package>
<package>
<name>seamonkey</name>
<name>linux-seamonkey</name>
<range><lt>2.53.0</lt></range>
</package>
<package>
<name>firefox-esr</name>
<range><lt>60.3.0,1</lt></range>
</package>
<package>
<name>linux-firefox</name>
<range><lt>60.3.0,2</lt></range>
</package>
<package>
<name>libxul</name>
<name>thunderbird</name>
<name>linux-thunderbird</name>
<range><lt>60.3.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-26/">
<p>CVE-2018-12391: HTTP Live Stream audio data is accessible cross-origin</p>
<p>CVE-2018-12392: Crash with nested event loops</p>
<p>CVE-2018-12393: Integer overflow during Unicode conversion while loading JavaScript</p>
<p>CVE-2018-12395: WebExtension bypass of domain restrictions through header rewriting</p>
<p>CVE-2018-12396: WebExtension content scripts can execute in disallowed contexts</p>
<p>CVE-2018-12397:</p>
<p>CVE-2018-12398: CSP bypass through stylesheet injection in resource URIs</p>
<p>CVE-2018-12399: Spoofing of protocol registration notification bar</p>
<p>CVE-2018-12400: Favicons are cached in private browsing mode on Firefox for Android</p>
<p>CVE-2018-12401: DOS attack through special resource URI parsing</p>
<p>CVE-2018-12402: SameSite cookies leak when pages are explicitly saved</p>
<p>CVE-2018-12403: Mixed content warning is not displayed when HTTPS page loads a favicon over HTTP</p>
<p>CVE-2018-12388: Memory safety bugs fixed in Firefox 63</p>
<p>CVE-2018-12390: Memory safety bugs fixed in Firefox 63 and Firefox ESR 60.3</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-12388</cvename>
<cvename>CVE-2018-12390</cvename>
<cvename>CVE-2018-12391</cvename>
<cvename>CVE-2018-12392</cvename>
<cvename>CVE-2018-12393</cvename>
<cvename>CVE-2018-12395</cvename>
<cvename>CVE-2018-12396</cvename>
<cvename>CVE-2018-12397</cvename>
<cvename>CVE-2018-12398</cvename>
<cvename>CVE-2018-12399</cvename>
<cvename>CVE-2018-12400</cvename>
<cvename>CVE-2018-12401</cvename>
<cvename>CVE-2018-12402</cvename>
<cvename>CVE-2018-12403</cvename>
<url>https://www.mozilla.org/en-US/security/advisories/mfsa2018-26/</url>
<url>https://www.mozilla.org/en-US/security/advisories/mfsa2018-27/</url>
</references>
<dates>
<discovery>2018-10-23</discovery>
<entry>2018-10-23</entry>
<modified>2019-07-23</modified>
</dates>
</vuln>
<vuln vid="140a14b5-d615-11e8-b3cb-00e04c1ea73d">
<topic>drupal -- Drupal Core - Multiple Vulnerabilities</topic>
<affects>
<package>
<name>drupal7</name>
<range><lt>7.60</lt></range>
</package>
<package>
<name>drupal8</name>
<range><lt>8.6.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Drupal Security Team reports:</p>
<blockquote cite="https://www.drupal.org/SA-CORE-2018-006">
<p>he path module allows users with the 'administer paths' to create pretty URLs
for content. In certain circumstances the user can enter a particular path that
triggers an open redirect to a malicious url.The issue is mitigated by the fact
that the user needs the administer paths permission to exploit.</p>
<p>When sending email some variables were not being sanitized for shell arguments,
which could lead to remote code execution. </p>
</blockquote>
</body>
</description>
<references>
<url>https://www.drupal.org/SA-CORE-2018-006</url>
</references>
<dates>
<discovery>2018-10-17</discovery>
<entry>2018-10-22</entry>
<modified>2018-11-04</modified>
</dates>
</vuln>
<vuln vid="afc60484-0652-440e-b01a-5ef814747f06">
<topic>ruby -- multiple vulnerabilities</topic>
<affects>
<package>
<name>ruby</name>
<range><ge>2.3.0,1</ge><lt>2.3.8,1</lt></range>
<range><ge>2.4.0,1</ge><lt>2.4.5,1</lt></range>
<range><ge>2.5.0,1</ge><lt>2.5.2,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Ruby news:</p>
<blockquote cite="https://www.ruby-lang.org/en/news/2018/10/17/ruby-2-5-2-released/">
<p>CVE-2018-16395: OpenSSL::X509::Name equality check does not work
correctly</p>
<p>An instance of OpenSSL::X509::Name contains entities such as CN, C and
so on. Some two instances of OpenSSL::X509::Name are equal only when
all entities are exactly equal. However, there is a bug that the
equality check is not correct if the value of an entity of the
argument (right-hand side) starts with the value of the receiver
(left-hand side). So, if a malicious X.509 certificate is passed to
compare with an existing certificate, there is a possibility to be
judged incorrectly that they are equal.</p>
<p>CVE-2018-16396: Tainted flags are not propagated in Array#pack and
String#unpack with some directives</p>
<p>Array#pack method converts the receiver's contents into a string with
specified format. If the receiver contains some tainted objects, the
returned string also should be tainted. String#unpack method which
converts the receiver into an array also should propagate its tainted
flag to the objects contained in the returned array. But, with B, b, H
and h directives, the tainted flags are not propagated. So, if a script
processes unreliable inputs by Array#pack and/or String#unpack with
these directives and checks the reliability with tainted flags, the
check might be wrong.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.ruby-lang.org/en/news/2018/10/17/ruby-2-5-2-released/</url>
<url>https://www.ruby-lang.org/en/news/2018/10/17/openssl-x509-name-equality-check-does-not-work-correctly-cve-2018-16395/</url>
<url>https://www.ruby-lang.org/en/news/2018/10/17/not-propagated-taint-flag-in-some-formats-of-pack-cve-2018-16396/</url>
<cvename>CVE-2018-16395</cvename>
<cvename>CVE-2018-16396</cvename>
</references>
<dates>
<discovery>2018-10-17</discovery>
<entry>2018-10-20</entry>
</dates>
</vuln>
<vuln vid="ec5072b0-d43a-11e8-a6d2-b499baebfeaf">
<topic>MySQL -- multiple vulnerabilities</topic>
<affects>
<package>
<name>mariadb55-server</name>
<range><lt>5.5.62</lt></range>
</package>
<package>
<name>mariadb100-server</name>
<range><lt>10.0.37</lt></range>
</package>
<package>
<name>mariadb101-server</name>
<range><lt>10.1.37</lt></range>
</package>
<package>
<name>mariadb102-server</name>
<range><lt>10.2.19</lt></range>
</package>
<package>
<name>mariadb103-server</name>
<range><lt>10.3.11</lt></range>
</package>
<package>
<name>mysql55-server</name>
<range><lt>5.5.62</lt></range>
</package>
<package>
<name>mysql56-server</name>
<range><lt>5.6.42</lt></range>
</package>
<package>
<name>mysql57-server</name>
<range><lt>5.7.24</lt></range>
</package>
<package>
<name>mysql80-server</name>
<range><lt>8.0.13</lt></range>
</package>
<package>
<name>percona55-server</name>
<range><lt>5.5.62</lt></range>
</package>
<package>
<name>percona56-server</name>
<range><lt>5.6.42</lt></range>
</package>
<package>
<name>percona57-server</name>
<range><lt>5.7.24</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Oracle reports:</p>
<blockquote cite="https://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html#AppendixMSQL">
<p>Please reference CVE/URL list for details</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html#AppendixMSQL</url>
<cvename>CVE-2016-9843</cvename>
<cvename>CVE-2018-3155</cvename>
<cvename>CVE-2018-3143</cvename>
<cvename>CVE-2018-3156</cvename>
<cvename>CVE-2018-3251</cvename>
<cvename>CVE-2018-3182</cvename>
<cvename>CVE-2018-3137</cvename>
<cvename>CVE-2018-3203</cvename>
<cvename>CVE-2018-3133</cvename>
<cvename>CVE-2018-3145</cvename>
<cvename>CVE-2018-3144</cvename>
<cvename>CVE-2018-3185</cvename>
<cvename>CVE-2018-3195</cvename>
<cvename>CVE-2018-3247</cvename>
<cvename>CVE-2018-3187</cvename>
<cvename>CVE-2018-3174</cvename>
<cvename>CVE-2018-3171</cvename>
<cvename>CVE-2018-3277</cvename>
<cvename>CVE-2018-3162</cvename>
<cvename>CVE-2018-3173</cvename>
<cvename>CVE-2018-3200</cvename>
<cvename>CVE-2018-3170</cvename>
<cvename>CVE-2018-3212</cvename>
<cvename>CVE-2018-3280</cvename>
<cvename>CVE-2018-3186</cvename>
<cvename>CVE-2018-3161</cvename>
<cvename>CVE-2018-3278</cvename>
<cvename>CVE-2018-3279</cvename>
<cvename>CVE-2018-3282</cvename>
<cvename>CVE-2018-3284</cvename>
<cvename>CVE-2018-3283</cvename>
<cvename>CVE-2018-3286</cvename>
</references>
<dates>
<discovery>2018-10-16</discovery>
<entry>2018-10-20</entry>
<modified>2018-11-08</modified>
</dates>
</vuln>
<vuln vid="44864c84-d3b8-11e8-b3cb-00e04c1ea73d">
<topic>matomo -- XSS vulnerability</topic>
<affects>
<package>
<name>matomo</name>
<range><lt>3.6.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Matomo reports:</p>
<blockquote cite="https://matomo.org/changelog/matomo-3-6-1/">
<p>Several XSS issues have been fixed thanks to the great work of security
researchers who responsible disclosed issues to us.</p>
</blockquote>
</body>
</description>
<references>
<url>https://matomo.org/changelog/matomo-3-6-1/</url>
</references>
<dates>
<discovery>2018-10-18</discovery>
<entry>2018-10-19</entry>
</dates>
</vuln>
<vuln vid="2383767c-d224-11e8-9623-a4badb2f4699">
<topic>libssh -- authentication bypass vulnerability</topic>
<affects>
<package>
<name>libssh</name>
<range><ge>0.6</ge><lt>0.7.6</lt></range>
<range><ge>0.8</ge><lt>0.8.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>gladiac reports:</p>
<blockquote cite="https://www.libssh.org/2018/10/16/libssh-0-8-4-and-0-7-6-security-and-bugfix-release/">
<p>libssh versions 0.6 and above have an authentication bypass
vulnerability in the server code. By presenting the server an
SSH2_MSG_USERAUTH_SUCCESS message in place of the
SSH2_MSG_USERAUTH_REQUEST message which the server would expect to
initiate authentication, the attacker could successfully authentciate
without any credentials.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.libssh.org/2018/10/16/libssh-0-8-4-and-0-7-6-security-and-bugfix-release/</url>
<cvename>CVE-2018-10933</cvename>
</references>
<dates>
<discovery>2018-10-16</discovery>
<entry>2018-10-17</entry>
</dates>
</vuln>
<vuln vid="8c08ab4c-d06c-11e8-b35c-001b217b3468">
<topic>Libgit2 -- multiple vulnerabilities</topic>
<affects>
<package>
<name>libgit2</name>
<range><lt>0.27.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Git community reports:</p>
<blockquote cite="https://github.com/libgit2/libgit2/releases/tag/v0.27.5">
<p>Multiple vulnerabilities.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/libgit2/libgit2/releases/tag/v0.27.5</url>
<cvename>CVE-2018-17456</cvename>
</references>
<dates>
<discovery>2018-10-05</discovery>
<entry>2018-10-15</entry>
</dates>
</vuln>
<vuln vid="4c11b51e-cd8d-11e8-b0cb-a0f3c100ae18">
<topic>Memory leak bug in Toxcore</topic>
<affects>
<package>
<name>toxcore</name>
<range><lt>0.2.8,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Tox project blog reports:</p>
<blockquote cite="https://blog.tox.chat/2018/10/memory-leak-bug-and-new-toxcore-release-fixing-it/">
<p>A memory leak bug was discovered in Toxcore that can be triggered remotely to
exhaust one’s system memory, resulting in a denial of service attack.
The bug is present in the TCP Server module of Toxcore and therefore it
affects mostly bootstrap nodes. Regular Tox clients generally have the
TCP Server functionality disabled by default, leaving them unaffected.</p>
</blockquote>
</body>
</description>
<references>
<url>https://blog.tox.chat/2018/10/memory-leak-bug-and-new-toxcore-release-fixing-it/</url>
</references>
<dates>
<discovery>2018-09-29</discovery>
<entry>2018-10-11</entry>
</dates>
</vuln>
<vuln vid="cb539d4e-cd68-11e8-8819-00e04c1ea73d">
<topic>gitea -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gitea</name>
<range><lt>1.5.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitea project reports:</p>
<blockquote cite="https://github.com/go-gitea/gitea/issues/4357">
<p>CSRF Vulnerability on API.</p>
<p>Enforce token on api routes.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/go-gitea/gitea/issues/4357</url>
<url>ttps://github.com/go-gitea/gitea/pull/4840</url>
</references>
<dates>
<discovery>2018-10-01</discovery>
<entry>2018-10-11</entry>
</dates>
</vuln>
<vuln vid="3350275d-cd5a-11e8-a7be-3497f683cb16">
<topic>jenkins -- multiple vulnerabilities</topic>
<affects>
<package>
<name>jenkins</name>
<range><lt>2.146</lt></range>
</package>
<package>
<name>jenkins-lts</name>
<range><lt>2.138.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Jenkins Security Advisory:</p>
<blockquote cite="https://jenkins.io/security/advisory/2018-10-10/">
<h1>Description</h1>
<h5>(Low) SECURITY-867</h5>
<p>Path traversal vulnerability in Stapler allowed accessing internal data</p>
<h5>(Medium) SECURITY-1074</h5>
<p>Arbitrary file write vulnerability using file parameter definitions</p>
<h5>(Medium) SECURITY-1129</h5>
<p>Reflected XSS vulnerability</p>
<h5>(Medium) SECURITY-1162</h5>
<p>Ephemeral user record was created on some invalid authentication attempts</p>
<h5>(Medium) SECURITY-1128</h5>
<p>Ephemeral user record creation</p>
<h5>(Medium) SECURITY-1158</h5>
<p>Session fixation vulnerability on user signup</p>
<h5>(Medium) SECURITY-765</h5>
<p>Failures to process form submission data could result in secrets being displayed or written to logs</p>
</blockquote>
</body>
</description>
<references>
<url>https://jenkins.io/security/advisory/2018-10-10/</url>
</references>
<dates>
<discovery>2018-10-10</discovery>
<entry>2018-10-11</entry>
</dates>
</vuln>
<vuln vid="a4eb38ea-cc06-11e8-ada4-408d5cf35399">
<topic>tinc -- Buffer overflow</topic>
<affects>
<package>
<name>tinc</name>
<range><lt>1.0.35</lt></range>
</package>
<package>
<name>tinc-devel</name>
<range><lt>1.1pre17</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>tinc-vpn.org reports:</p>
<blockquote cite="http://www.tinc-vpn.org/news/">
<p>The authentication protocol allows an oracle attack that could
potentially be exploited.</p>
<p>If a man-in-the-middle has intercepted the TCP connection it
might be able to force plaintext UDP packets between two nodes for up to
a PingInterval period.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.tinc-vpn.org/git/browse?p=tinc;a=commit;h=d3297fbd3b8c8c8a4661f5bbf89aca5cacba8b5a</url>
<url>https://www.tinc-vpn.org/git/browse?p=tinc;a=commit;h=e97943b7cc9c851ae36f5a41e2b6102faa74193f</url>
<cvename>CVE-2018-16737</cvename>
<cvename>CVE-2018-16738</cvename>
<cvename>CVE-2018-16758</cvename>
</references>
<dates>
<discovery>2018-10-08</discovery>
<entry>2018-10-09</entry>
</dates>
</vuln>
<vuln vid="23413442-c8ea-11e8-b35c-001b217b3468">
<topic>Gitlab -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>11.3.0</ge><lt>11.3.4</lt></range>
<range><ge>11.2.0</ge><lt>11.2.5</lt></range>
<range><ge>10.2.0</ge><lt>11.1.8</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/10/05/critical-security-release-11-3-4/">
<p>Merge request information disclosure</p>
<p>Private project namespace information disclosure</p>
<p>Gitlab Flavored Markdown API information disclosure</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/10/05/critical-security-release-11-3-4/</url>
<cvename>CVE-2018-17939</cvename>
<cvename>CVE-2018-17976</cvename>
<cvename>CVE-2018-17975</cvename>
</references>
<dates>
<discovery>2018-10-05</discovery>
<entry>2018-10-05</entry>
</dates>
</vuln>
<vuln vid="8b812395-c739-11e8-ab5b-9c5c8e75236a">
<topic>clamav -- multiple vulnerabilities</topic>
<affects>
<package>
<name>clamav</name>
<range><lt>0.100.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p> Joel Esler reports:</p>
<blockquote cite="https://blog.clamav.net/2018/10/clamav-01002-has-been-released.html">
<ul>
<li>CVE-2018-15378:
<ul>
<li>Vulnerability in ClamAV's MEW unpacking feature that could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device.</li>
<li>Reported by Secunia Research at Flexera.</li>
</ul>
</li>
<li>Fix for a 2-byte buffer over-read bug in ClamAV&s PDF parsing code.
<ul>
<li>Reported by Alex Gaynor.</li>
</ul>
</li>
<li>CVE-2018-14680:
<ul>
<li>An issue was discovered in mspack/chmd.c in libmspack before 0.7alpha. It does not reject blank CHM filenames.</li>
</ul>
</li>
<li>CVE-2018-14681:
<ul>
<li>An issue was discovered in kwajd_read_headers in mspack/kwajd.c in libmspack before 0.7alpha. Bad KWAJ file header extensions could cause a one or two byte overwrite.</li>
</ul>
</li>
<li>CVE-2018-14682:
<ul>
<li>An issue was discovered in mspack/chmd.c in libmspack before 0.7alpha. There is an off-by-one error in the TOLOWER() macro for CHM decompression. Additionally, 0.100.2 reverted 0.100.1's patch for CVE-2018-14679, and applied libmspack's version of the fix in its place.</li>
</ul>
</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://blog.clamav.net/2018/10/clamav-01002-has-been-released.html</url>
<cvename>CVE-2018-15378</cvename>
<cvename>CVE-2018-14680</cvename>
<cvename>CVE-2018-14681</cvename>
<cvename>CVE-2018-14682</cvename>
</references>
<dates>
<discovery>2018-10-03</discovery>
<entry>2018-10-03</entry>
<modified>2020-06-24</modified>
</dates>
</vuln>
<vuln vid="004d8c23-c710-11e8-98c7-000c29434208">
<topic>Django -- password hash disclosure</topic>
<affects>
<package>
<name>py34-django21</name>
<name>py35-django21</name>
<name>py36-django21</name>
<name>py37-django21</name>
<range><lt>2.1.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Django release notes:</p>
<blockquote cite="https://docs.djangoproject.com/en/2.1/releases/2.1.2/">
<p>CVE-2018-16984: Password hash disclosure to "view only" admin users</p>
<p>If an admin user has the change permission to the user model, only part
of the password hash is displayed in the change form. Admin users with the
view (but not change) permission to the user model were displayed the entire
hash. While it's typically infeasible to reverse a strong password hash, if
your site uses weaker password hashing algorithms such as MD5 or SHA1, it
could be a problem.</p>
</blockquote>
</body>
</description>
<references>
<url>https://docs.djangoproject.com/en/2.1/releases/2.1.2/</url>
<cvename>CVE-2018-16984</cvename>
</references>
<dates>
<discovery>2018-10-02</discovery>
<entry>2018-10-03</entry>
</dates>
</vuln>
<vuln vid="c4f39920-781f-4aeb-b6af-17ed566c4272">
<topic>mozilla -- multiple vulnerabilities</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>62.0.3,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.2.4</lt></range>
</package>
<package>
<name>seamonkey</name>
<name>linux-seamonkey</name>
<range><lt>2.53.0</lt></range>
</package>
<package>
<name>firefox-esr</name>
<range><lt>60.2.2,1</lt></range>
</package>
<package>
<name>linux-firefox</name>
<range><lt>60.2.2,2</lt></range>
</package>
<package>
<name>libxul</name>
<name>thunderbird</name>
<name>linux-thunderbird</name>
<range><lt>60.2.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-24/">
<h1>CVE-2018-12386: Type confusion in JavaScript</h1>
<p>A vulnerability in register allocation in JavaScript can
lead to type confusion, allowing for an arbitrary read and
write. This leads to remote code execution inside the
sandboxed content process when triggered.</p>
<h1>CVE-2018-12387: </h1>
<p>A vulnerability where the JavaScript JIT compiler inlines
Array.prototype.push with multiple arguments that results
in the stack pointer being off by 8 bytes after a
bailout. This leaks a memory address to the calling
function which can be used as part of an exploit inside
the sandboxed content process.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-12386</cvename>
<cvename>CVE-2018-12387</cvename>
<url>https://www.mozilla.org/en-US/security/advisories/mfsa2018-24/</url>
</references>
<dates>
<discovery>2018-10-02</discovery>
<entry>2018-10-02</entry>
<modified>2019-07-23</modified>
</dates>
</vuln>
<vuln vid="065b3b72-c5ab-11e8-9ae2-001b217b3468">
<topic>Gitlab -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>11.3.0</ge><lt>11.3.1</lt></range>
<range><ge>11.2.0</ge><lt>11.2.4</lt></range>
<range><ge>7.6.0</ge><lt>11.1.7</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/10/01/security-release-gitlab-11-dot-3-dot-1-released/">
<p>SSRF GCP access token disclosure</p>
<p>Persistent XSS on issue details</p>
<p>Diff formatter DoS in Sidekiq jobs</p>
<p>Confidential information disclosure in events API endpoint</p>
<p>validate_localhost function in url_blocker.rb could be bypassed</p>
<p>Slack integration CSRF Oauth2</p>
<p>GRPC::Unknown logging token disclosure</p>
<p>IDOR merge request approvals</p>
<p>Persistent XSS package.json</p>
<p>Persistent XSS merge request project import</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/10/01/security-release-gitlab-11-dot-3-dot-1-released/</url>
<cvename>CVE-2018-17450</cvename>
<cvename>CVE-2018-17454</cvename>
<cvename>CVE-2018-15472</cvename>
<cvename>CVE-2018-17449</cvename>
<cvename>CVE-2018-17452</cvename>
<cvename>CVE-2018-17451</cvename>
<cvename>CVE-2018-17453</cvename>
<cvename>CVE-2018-17455</cvename>
<cvename>CVE-2018-17537</cvename>
<cvename>CVE-2018-17536</cvename>
</references>
<dates>
<discovery>2018-10-01</discovery>
<entry>2018-10-01</entry>
</dates>
</vuln>
<vuln vid="5a757a31-f98e-4bd4-8a85-f1c0f3409769">
<topic>pango -- remote DoS vulnerability</topic>
<affects>
<package>
<name>pango</name>
<range><lt>1.42.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15120">
<p>libpango in Pango 1.40.8 through 1.42.3, as used in hexchat and other products, allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via crafted text with invalid Unicode sequences.</p>
</blockquote>
</body>
</description>
<references>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15120</url>
<url>https://www.exploit-db.com/exploits/45263/</url>
<url>https://mail.gnome.org/archives/distributor-list/2018-August/msg00001.html</url>
<url>https://github.com/GNOME/pango/commit/71aaeaf020340412b8d012fe23a556c0420eda5f</url>
<cvename>CVE-2018-15120</cvename>
</references>
<dates>
<discovery>2018-08-06</discovery>
<entry>2018-10-01</entry>
</dates>
</vuln>
<vuln vid="01018916-c47c-11e8-8b07-00e04c1ea73d">
<topic>Serendipity -- multiple vulnerabilities</topic>
<affects>
<package>
<name>serendipity</name>
<range><lt>2.1.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Serendipity reports:</p>
<blockquote cite="https://blog.s9y.org/archives/280-Serendipity-2.1.4-and-2.2.1-alpha1-released.html">
<p>Security: Fix XSS for pagination, when multi-category selection is used.</p>
</blockquote>
</body>
</description>
<references>
<url>https://blog.s9y.org/archives/280-Serendipity-2.1.4-and-2.2.1-alpha1-released.html</url>
</references>
<dates>
<discovery>2018-09-20</discovery>
<entry>2018-09-30</entry>
</dates>
</vuln>
<vuln vid="40a844bf-c430-11e8-96dc-000743165db0">
<topic>bitcoin -- Denial of Service and Possible Mining Inflation</topic>
<affects>
<package>
<name>bitcoin</name>
<name>bitcoin-daemon</name>
<range><lt>0.16.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Bitcoin Core reports:</p>
<blockquote cite="https://bitcoincore.org/en/2018/09/20/notice/">
<p>CVE-2018-17144, a fix for which was released on September 18th in Bitcoin Core versions 0.16.3 and 0.17.0rc4, includes both a Denial of Service component and a critical inflation vulnerability. It was originally reported to several developers working on Bitcoin Core, as well as projects supporting other cryptocurrencies, including ABC and Unlimited on September 17th as a Denial of Service bug only, however we quickly determined that the issue was also an inflation vulnerability with the same root cause and fix.</p>
</blockquote>
</body>
</description>
<references>
<url>https://bitcoincore.org/en/2018/09/20/notice/</url>
<cvename>CVE-2018-17144</cvename>
</references>
<dates>
<discovery>2018-09-17</discovery>
<entry>2018-09-29</entry>
</dates>
</vuln>
<vuln vid="613193a0-c1b4-11e8-ae2d-54e1ad3d6335">
<topic>spamassassin -- multiple vulnerabilities</topic>
<affects>
<package>
<name>spamassassin</name>
<range><lt>3.4.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>the Apache Spamassassin project reports:</p>
<blockquote cite="https://seclists.org/oss-sec/2018/q3/242">
<p>In Apache SpamAssassin, using HTML::Parser, we setup an object and
hook into the begin and end tag event handlers In both cases, the
"open" event is immediately followed by a "close" event - even if
the tag *does not* close in the HTML being parsed.</p>
<p>Because of this, we are missing the "text" event to deal with
the object normally. This can cause carefully crafted emails that
might take more scan time than expected leading to a Denial of
Service.</p>
<p>Fix a reliance on "." in @INC in one configuration script. Whether
this can be exploited in any way is uncertain.</p>
<p>Fix a potential Remote Code Execution bug with the PDFInfo plugin.
Thanks to cPanel Security Team for their report of this issue.</p>
<p> Fourth, this release fixes a local user code injection in the
meta rule syntax. Thanks again to cPanel Security Team for their
report of this issue.</p>
</blockquote>
</body>
</description>
<references>
<url>https://seclists.org/oss-sec/2018/q3/242</url>
<cvename>CVE-2017-15705</cvename>
<cvename>CVE-2016-1238</cvename>
<cvename>CVE-2018-11780</cvename>
<cvename>CVE-2018-11781</cvename>
</references>
<dates>
<discovery>2018-09-16</discovery>
<entry>2018-09-26</entry>
</dates>
</vuln>
<vuln vid="bad59128-c188-11e8-9d40-f0def10dca57">
<topic>wesnoth -- Code Injection vulnerability</topic>
<affects>
<package>
<name>wesnoth</name>
<range><ge>1.7.0</ge><lt>1.14.4,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>shadowm reports:</p>
<blockquote cite="https://forums.wesnoth.org/viewtopic.php?t=48528">
<p>A severe bug was found in the game client which could allow a malicious user to execute arbitrary code through the Lua engine by using specially-crafted code in add-ons, saves, replays, or networked games. This issue affects all platforms and all existing releases since Wesnoth version 1.7.0.
Users of all previous version should upgrade immediately.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-1999023</cvename>
<url>https://gist.github.com/shikadiqueen/45951ddc981cf8e0d9a74e4b30400380</url>
</references>
<dates>
<discovery>2018-07-14</discovery>
<entry>2018-09-26</entry>
</dates>
</vuln>
<vuln vid="e182c076-c189-11e8-a6d2-b499baebfeaf">
<topic>Apache -- Denial of service vulnerability in HTTP/2</topic>
<affects>
<package>
<name>apache24</name>
<range><lt>2.4.35</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Apache httpd project reports:</p>
<blockquote cite="http://httpd.apache.org/security/vulnerabilities_24.html">
<p>low: DoS for HTTP/2 connections by continuous SETTINGS</p>
<p>By sending continous SETTINGS frames of maximum size an ongoing
HTTP/2 connection could be kept busy and would never time out. This
can be abused for a DoS on the server. This only affect a server
that has enabled the h2 protocol.</p>
</blockquote>
</body>
</description>
<references>
<url>http://httpd.apache.org/security/vulnerabilities_24.html</url>
<cvename>CVE-2018-11763</cvename>
</references>
<dates>
<discovery>2018-09-25</discovery>
<entry>2018-09-26</entry>
</dates>
</vuln>
<vuln vid="6bf71117-c0c9-11e8-b760-6023b685b1ee">
<topic>mantis -- XSS vulnerability</topic>
<affects>
<package>
<name>mantis-php56</name>
<name>mantis-php70</name>
<name>mantis-php71</name>
<name>mantis-php72</name>
<range><lt>2.17.1,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Brian Carpenter reports:</p>
<blockquote cite="https://mantisbt.org/bugs/view.php?id=24731">
<p>Reflected XSS in view_filters_page.php via core/filter_form_api.php</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-16514</cvename>
</references>
<dates>
<discovery>2018-09-03</discovery>
<entry>2018-09-25</entry>
</dates>
</vuln>
<vuln vid="2d6de6a8-fb78-4149-aeda-77fc8f140f06">
<topic>smart_proxy_dynflow -- authentication bypass vulnerability</topic>
<affects>
<package>
<name>rubygem-smart_proxy_dynflow</name>
<range><lt>0.2.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>MITRE reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14643">
<p>An authentication bypass flaw was found in the smart_proxy_dynflow
component used by Foreman. A malicious attacker can use this flaw to
remotely execute arbitrary commands on machines managed by vulnerable
Foreman instances, in a highly privileged context.</p>
</blockquote>
</body>
</description>
<references>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14643</url>
<url>https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-14643</url>
<cvename>CVE-2018-14643</cvename>
</references>
<dates>
<discovery>2018-09-20</discovery>
<entry>2018-09-22</entry>
</dates>
</vuln>
<vuln vid="be1aada2-be6c-11e8-8fc6-000c29434208">
<topic>mediawiki -- multiple vulnerabilities</topic>
<affects>
<package>
<name>mediawiki127</name>
<range><lt>1.27.5</lt></range>
</package>
<package>
<name>mediawiki129</name>
<range><le>1.29.3</le></range>
</package>
<package>
<name>mediawiki130</name>
<range><lt>1.30.1</lt></range>
</package>
<package>
<name>mediawiki131</name>
<range><lt>1.31.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mediawiki reports:</p>
<blockquote cite="https://lists.wikimedia.org/pipermail/mediawiki-announce/2018-September/000223.html">
<p>Security fixes:</p>
<p>T169545: $wgRateLimits entry for 'user' overrides 'newbie'.</p>
<p>T194605: BotPasswords can bypass CentralAuth's account lock.</p>
<p>T187638: When a log event is (partially) hidden Special:Redirect/logid
can link to the incorrect log and reveal hidden</p>
<p>T193237: Special:BotPasswords should require reauthenticate.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-0503</cvename>
<cvename>CVE-2018-0505</cvename>
<cvename>CVE-2018-0504</cvename>
<url>https://lists.wikimedia.org/pipermail/mediawiki-announce/2018-September/000223.html</url>
</references>
<dates>
<discovery>2018-08-29</discovery>
<entry>2018-09-22</entry>
</dates>
</vuln>
<vuln vid="3284d948-140c-4a3e-aa76-3b440e2006a8">
<topic>firefox -- Crash in TransportSecurityInfo due to cached data</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>62.0.2,1</lt></range>
</package>
<package>
<name>firefox-esr</name>
<range><lt>60.2.1,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-22/">
<p>A potentially exploitable crash in TransportSecurityInfo used for SSL can be triggered by data stored in the local cache in the user profile directory. This issue is only exploitable in combination with another vulnerability allowing an attacker to write data into the local cache or from locally installed malware. This issue also triggers a non-exploitable startup crash for users switching between the Nightly and Release versions of Firefox if the same profile is used.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-12385</cvename>
<url>https://www.mozilla.org/security/advisories/mfsa2018-22/</url>
</references>
<dates>
<discovery>2018-09-21</discovery>
<entry>2018-09-21</entry>
</dates>
</vuln>
<vuln vid="77f67b46-bd75-11e8-81b6-001999f8d30b">
<topic>asterisk -- Remote crash vulnerability in HTTP websocket upgrade</topic>
<affects>
<package>
<name>asterisk13</name>
<range><lt>13.23.1</lt></range>
</package>
<package>
<name>asterisk15</name>
<range><lt>15.6.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Asterisk project reports:</p>
<blockquote cite="http://www.asterisk.org/downloads/security-advisories">
<p>There is a stack overflow vulnerability in the
res_http_websocket.so module of Asterisk that allows an
attacker to crash Asterisk via a specially crafted HTTP
request to upgrade the connection to a websocket. The
attackers request causes Asterisk to run out of stack
space and crash.</p>
<p>As a workaround disable HTTP websocket access by not
loading the res_http_websocket.so module.</p>
</blockquote>
</body>
</description>
<references>
<url>https://downloads.asterisk.org/pub/security/AST-2018-009.html</url>
<cvename>CVE-2018-17281</cvename>
</references>
<dates>
<discovery>2018-08-16</discovery>
<entry>2018-09-21</entry>
</dates>
</vuln>
<vuln vid="074cb225-bb2d-11e8-90e1-fcaa147e860e">
<topic>moodle -- multiple vulnerabilities</topic>
<affects>
<package>
<name>moodle31</name>
<range><lt>3.1.14</lt></range>
</package>
<package>
<name>moodle33</name>
<range><lt>3.3.8</lt></range>
</package>
<package>
<name>moodle34</name>
<range><lt>3.4.5</lt></range>
</package>
<package>
<name>moodle35</name>
<range><lt>3.5.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>moodle reports:</p>
<blockquote cite="https://moodle.org/mod/forum/discuss.php?d=376023">
<p>Moodle XML import of ddwtos could lead to intentional remote code
execution</p>
<p>QuickForm library remote code vulnerability (upstream)</p>
<p>Boost theme - blog search GET parameter insufficiently filtered</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-14630</cvename>
<cvename>CVE-2018-1999022</cvename>
<cvename>CVE-2018-14631</cvename>
<url>https://moodle.org/mod/forum/discuss.php?d=376023</url>
</references>
<dates>
<discovery>2018-09-05</discovery>
<entry>2018-09-18</entry>
</dates>
</vuln>
<vuln vid="bf2b9c56-b93e-11e8-b2a8-a4badb296695">
<topic>joomla3 -- vulnerabilitiesw</topic>
<affects>
<package>
<name>joomla3</name>
<range><lt>3.8.12</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>JSST reports: Multiple low-priority Vulnerabilities</p>
<blockquote cite="https://developer.joomla.org/security-centre/743-20180801-core-hardening-the-inputfilter-for-phar-stubs.html">
<p>Inadequate checks in the InputFilter class could allow specifically prepared PHAR files to pass the upload filter.</p>
</blockquote>
<blockquote cite="https://developer.joomla.org/security-centre/744-20180802-core-stored-xss-vulnerability-in-the-frontend-profile.html">
<p>Inadequate output filtering on the user profile page could lead to a stored XSS attack.</p>
</blockquote>
<blockquote cite="https://developer.joomla.org/security-centre/745-20180803-core-acl-violation-in-custom-fields.html">
<p>Inadequate checks regarding disabled fields can lead to an ACL violation.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-15860</cvename>
<cvename>CVE-2018-15881</cvename>
<cvename>CVE-2018-15882</cvename>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15880</url>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15881</url>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15882</url>
<url>https://developer.joomla.org/security-centre/743-20180801-core-hardening-the-inputfilter-for-phar-stubs.html</url>
<url>https://developer.joomla.org/security-centre/744-20180802-core-stored-xss-vulnerability-in-the-frontend-profile.html</url>
<url>https://developer.joomla.org/security-centre/745-20180803-core-acl-violation-in-custom-fields.html</url>
</references>
<dates>
<discovery>2018-08-23</discovery>
<entry>2018-09-15</entry>
</dates>
</vuln>
<vuln vid="ab38d9f8-b787-11e8-8e7a-00e04c1ea73d">
<topic>mybb -- vulnerabilities</topic>
<affects>
<package>
<name>mybb</name>
<range><lt>1.8.19</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>mybb Team reports:</p>
<blockquote cite="https://blog.mybb.com/2018/09/11/mybb-1-8-19-released-security-maintenance-release/">
<p>High risk: Email field SQL Injection.</p>
<p>Medium risk: Video MyCode Persistent XSS in Visual Editor.</p>
<p>Low risk: Insufficient permission check in User CP’s attachment management.</p>
<p>Low risk: Insufficient email address verification.</p>
</blockquote>
</body>
</description>
<references>
<url>https://blog.mybb.com/2018/09/11/mybb-1-8-19-released-security-maintenance-release/</url>
</references>
<dates>
<discovery>2018-09-11</discovery>
<entry>2018-09-13</entry>
</dates>
</vuln>
<vuln vid="a67c122a-b693-11e8-ac58-a4badb2f4699">
<topic>FreeBSD -- Improper ELF header parsing</topic>
<affects>
<package>
<name>FreeBSD-kernel</name>
<range><ge>11.2</ge><lt>11.2_3</lt></range>
<range><ge>11.1</ge><lt>11.1_14</lt></range>
<range><ge>10.4</ge><lt>10.4_12</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>Insufficient validation was performed in the ELF header
parser, and malformed or otherwise invalid ELF binaries
were not rejected as they should be.</p>
<h1>Impact:</h1>
<p>Execution of a malicious ELF binary may result in a
kernel crash or may disclose kernel memory.</p>
</body>
</description>
<references>
<cvename>CVE-2018-6924</cvename>
<freebsdsa>SA-18:12.elf</freebsdsa>
</references>
<dates>
<discovery>2018-09-12</discovery>
<entry>2018-09-12</entry>
</dates>
</vuln>
<vuln vid="fe818607-b5ff-11e8-856b-485b3931c969">
<topic>Containous Traefik -- exposes the configuration and secret</topic>
<affects>
<package>
<name>traefik</name>
<range><lt>1.6.6</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>MITRE reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15598">
<p>Containous Traefik 1.6.x before 1.6.6, when --api is used, exposes the
configuration and secret if authentication is missing and the API's port
is publicly reachable.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-15598</cvename>
<url>https://github.com/containous/traefik/pull/3790</url>
<url>https://github.com/containous/traefik/releases/tag/v1.6.6</url>
</references>
<dates>
<discovery>2018-08-20</discovery>
<entry>2018-09-11</entry>
</dates>
</vuln>
<vuln vid="f9d73a20-b5f0-11e8-b1da-6451062f0f7a">
<topic>Flash Player -- information disclosure</topic>
<affects>
<package>
<name>linux-flashplayer</name>
<range><lt>31.0.0.108</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Adobe reports:</p>
<blockquote cite="https://helpx.adobe.com/security/products/flash-player/apsb18-31.html">
<ul>
<li>This update resolves a privilege escalation vulnerability that
could lead to information disclosure (CVE-2018-15967).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-15967</cvename>
<url>https://helpx.adobe.com/security/products/flash-player/apsb18-31.html</url>
</references>
<dates>
<discovery>2018-09-11</discovery>
<entry>2018-09-11</entry>
</dates>
</vuln>
<vuln vid="337960ec-b5dc-11e8-ac58-a4badb2f4699">
<topic>Plex Media Server -- Information Disclosure Vulnerability</topic>
<affects>
<package>
<name>plexmediaserver</name>
<name>plexmediaserver-plexpass</name>
<range><lt>1.13.5.5332</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Chris reports:</p>
<blockquote cite="https://seclists.org/fulldisclosure/2018/Aug/1">
<p>The XML parsing engine for Plex Media Server's SSDP/UPNP
functionality is vulnerable to an XML External Entity
Processing (XXE) attack. Unauthenticated attackers on the same LAN can
use this vulnerability to:</p>
<ul>
<li>Access arbitrary files from the filesystem with the same permission as
the user account running Plex.</li>
<li>Initiate SMB connections to capture NetNTLM challenge/response and
crack to clear-text password.</li>
<li>Initiate SMB connections to relay NetNTLM challenge/response and
achieve Remote Command Execution in Windows domains.</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://seclists.org/fulldisclosure/2018/Aug/1</url>
<cvename>CVE-2018-13415</cvename>
</references>
<dates>
<discovery>2018-08-01</discovery>
<entry>2018-09-11</entry>
</dates>
</vuln>
<vuln vid="f00acdec-b59f-11e8-805d-001e2a3f778d">
<topic>X11 Session -- SDDM allows unauthorised unlocking</topic>
<affects>
<package>
<name>sddm</name>
<range><lt>0.17.0_1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>MITRE reports:</p>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2018-14345">
<p>An issue was discovered in SDDM through 0.17.0. If configured with ReuseSession=true, the password is not checked for users with an already existing session. Any user with access to the system D-Bus can therefore unlock any graphical session.</p>
</blockquote>
<p>The default configuration of SDDM on FreeBSD is not affected, since it has ReuseSession=false.</p>
</body>
</description>
<references>
<url>https://www.suse.com/security/cve/CVE-2018-14345/</url>
<cvename>CVE-2018-14345</cvename>
</references>
<dates>
<discovery>2018-08-13</discovery>
<entry>2018-09-11</entry>
</dates>
</vuln>
<vuln vid="db2acdac-b5a7-11e8-8f6f-00e04c1ea73d">
<topic>mybb -- vulnerabilities</topic>
<affects>
<package>
<name>mybb</name>
<range><lt>1.8.18</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>mybb Team reports:</p>
<blockquote cite="https://blog.mybb.com/2018/08/22/mybb-1-8-18-released-security-maintenance-release/">
<p>High risk: Image MyCode “alt” attribute persistent XSS.</p>
<p>Medium risk: RSS Atom 1.0 item title persistent XSS.</p>
</blockquote>
</body>
</description>
<references>
<url>https://blog.mybb.com/2018/08/22/mybb-1-8-18-released-security-maintenance-release/</url>
</references>
<dates>
<discovery>2018-08-22</discovery>
<entry>2018-09-11</entry>
</dates>
</vuln>
<vuln vid="7c750960-b129-11e8-9fcd-080027f43a02">
<topic>Information disclosure - Gitea leaks email addresses</topic>
<affects>
<package>
<name>gitea</name>
<range><lt>1.5.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Gitea project reports:</p>
<blockquote cite="https://github.com/go-gitea/gitea/issues/4417">
<p>[Privacy] Gitea leaks hidden email addresses #4417</p>
<p>A fix has been implemented in Gitea 1.5.1.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/go-gitea/gitea/issues/4417</url>
<url>https://github.com/go-gitea/gitea/pull/4784</url>
</references>
<dates>
<discovery>2018-07-10</discovery>
<entry>2018-09-05</entry>
</dates>
</vuln>
<vuln vid="2a92555f-a6f8-11e8-8acd-10c37b4ac2ea">
<topic>links -- denial of service</topic>
<affects>
<package>
<name>links</name>
<range><lt>2.16,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>NIST reports:</p>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2017-11114">
<p>The put_chars function in html_r.c in Twibright Links 2.14 allows
remote attackers to cause a denial of service (buffer over-read)
via a crafted HTML file.</p>
</blockquote>
</body>
</description>
<references>
<url>https://nvd.nist.gov/vuln/detail/CVE-2017-11114</url>
<cvename>CVE-2017-11114</cvename>
</references>
<dates>
<discovery>2017-07-31</discovery>
<entry>2018-08-23</entry>
</dates>
</vuln>
<vuln vid="f4d638b9-e6e5-4dbe-8c70-571dbc116174">
<topic>curl -- password overflow vulnerability</topic>
<affects>
<package>
<name>curl</name>
<range><ge>7.15.4</ge><lt>7.61.1</lt></range>
</package>
<package>
<name>linux-c7-curl</name>
<range><lt>7.29.0_6</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>curl security problems:</p>
<blockquote cite="https://curl.haxx.se/docs/security.html">
<p>CVE-2018-14618: NTLM password overflow via integer overflow</p>
<p>The internal function Curl_ntlm_core_mk_nt_hash multiplies the length
of the password by two (SUM) to figure out how large temporary storage
area to allocate from the heap.</p>
<p>The length value is then subsequently used to iterate over the
password and generate output into the allocated storage buffer. On
systems with a 32 bit size_t, the math to calculate SUM triggers an
integer overflow when the password 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.</p>
<p>This bug is almost identical to CVE-2017-8816.</p>
</blockquote>
</body>
</description>
<references>
<url>https://curl.haxx.se/docs/security.html</url>
<url>https://curl.haxx.se/docs/CVE-2018-14618.html</url>
<cvename>CVE-2018-14618</cvename>
</references>
<dates>
<discovery>2018-09-05</discovery>
<entry>2018-09-05</entry>
<modified>2019-08-03</modified>
</dates>
</vuln>
<vuln vid="c96d416a-eae7-4d5d-bc84-40deca9329fb">
<topic>mozilla -- multiple vulnerabilities</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>62.0_1,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.2.3</lt></range>
</package>
<package>
<name>seamonkey</name>
<name>linux-seamonkey</name>
<range><lt>2.49.5</lt></range>
</package>
<package>
<name>firefox-esr</name>
<range><lt>60.2.0_1,1</lt></range>
</package>
<package>
<name>linux-firefox</name>
<range><lt>60.2.0,2</lt></range>
</package>
<package>
<name>libxul</name>
<name>thunderbird</name>
<name>linux-thunderbird</name>
<range><lt>60.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-20/">
<p>CVE-2018-12377: Use-after-free in refresh driver timers</p>
<p>CVE-2018-12378: Use-after-free in IndexedDB</p>
<p>CVE-2018-12379: Out-of-bounds write with malicious MAR file</p>
<p>CVE-2017-16541: Proxy bypass using automount and autofs</p>
<p>CVE-2018-12381: Dragging and dropping Outlook email message results in page navigation</p>
<p>CVE-2018-12382: Addressbar spoofing with javascript URI on Firefox for Android</p>
<p>CVE-2018-12383: Setting a master password post-Firefox 58 does not delete unencrypted previously stored passwords</p>
<p>CVE-2018-12375: Memory safety bugs fixed in Firefox 62</p>
<p>CVE-2018-12376: Memory safety bugs fixed in Firefox 62 and Firefox ESR 60.2</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-16541</cvename>
<cvename>CVE-2018-12375</cvename>
<cvename>CVE-2018-12376</cvename>
<cvename>CVE-2018-12377</cvename>
<cvename>CVE-2018-12378</cvename>
<cvename>CVE-2018-12379</cvename>
<cvename>CVE-2018-12381</cvename>
<cvename>CVE-2018-12382</cvename>
<cvename>CVE-2018-12383</cvename>
<url>https://www.mozilla.org/en-US/security/advisories/mfsa2018-20/</url>
<url>https://www.mozilla.org/en-US/security/advisories/mfsa2018-21/</url>
</references>
<dates>
<discovery>2018-09-05</discovery>
<entry>2018-09-05</entry>
<modified>2018-09-15</modified>
</dates>
</vuln>
<vuln vid="30c0f878-b03e-11e8-be8a-0011d823eebd">
<topic>Ghostscript -- arbitrary code execution</topic>
<affects>
<package>
<name>ghostscript9-agpl-base</name>
<name>ghostscript9-agpl-x11</name>
<range><lt>9.24</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>CERT reports:</p>
<blockquote cite="https://www.kb.cert.org/vuls/id/332928">
<p>Ghostscript contains an optional -dSAFER option, which is supposed
to prevent unsafe PostScript operations. Multiple PostScript
operations bypass the protections provided by -dSAFER, which can
allow an attacker to execute arbitrary commands with arbitrary
arguments. This vulnerability can also be exploited in applications
that leverage Ghostscript, such as ImageMagick, GraphicsMagick,
evince, Okular, Nautilus, and others.</p>
<p>Exploit code for this vulnerability is publicly available.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.kb.cert.org/vuls/id/332928</url>
<cvename>CVE-2018-15908</cvename>
<cvename>CVE-2018-15909</cvename>
<cvename>CVE-2018-15910</cvename>
<cvename>CVE-2018-15911</cvename>
</references>
<dates>
<discovery>2018-08-21</discovery>
<entry>2018-09-04</entry>
</dates>
</vuln>
<vuln vid="1f8d5806-ac51-11e8-9cb6-10c37b4ac2ea">
<topic>grafana -- LDAP and OAuth login vulnerability</topic>
<affects>
<package>
<name>grafana5</name>
<range><ge>5.0.0</ge><lt>5.2.3</lt></range>
</package>
<package>
<name>grafana4</name>
<range><ge>4.0.0</ge><lt>4.6.4</lt></range>
</package>
<package>
<name>grafana3</name>
<range><ge>3.0.0</ge></range>
</package>
<package>
<name>grafana2</name>
<range><ge>2.0.0</ge></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Grafana Labs reports:</p>
<blockquote cite="https://community.grafana.com/t/grafana-5-2-3-and-4-6-4-security-update/10050">
<p>On the 20th of August at 1800 CEST we were contacted about a
potential security issue with the “remember me” cookie Grafana
sets upon login. The issue targeted users without a local Grafana
password (LDAP & OAuth users) and enabled a potential attacker
to generate a valid cookie knowing only a username.</p>
<p>All installations which use the Grafana LDAP or OAuth
authentication features must be upgraded as soon as possible. If
you cannot upgrade, you should switch authentication mechanisms
or put additional protections in front of Grafana such as a
reverse proxy.</p>
</blockquote>
</body>
</description>
<references>
<url>https://community.grafana.com/t/grafana-5-2-3-and-4-6-4-security-update/10050</url>
<cvename>CVE-2018-558213</cvename>
</references>
<dates>
<discovery>2018-08-20</discovery>
<entry>2018-08-31</entry>
</dates>
</vuln>
<vuln vid="ffeb25d0-ac94-11e8-ab15-d8cb8abf62dd">
<topic>Gitlab -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>11.2.0</ge><lt>11.2.3</lt></range>
<range><ge>11.1.0</ge><lt>11.1.6</lt></range>
<range><ge>2.7.0</ge><lt>11.0.6</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/08/28/security-release-gitlab-11-dot-2-dot-2-released/">
<p>Persistent XSS in Pipeline Tooltip</p>
<p>GitLab.com GCP Endpoints Exposure</p>
<p>Persistent XSS in Merge Request Changes View</p>
<p>Sensitive Data Disclosure in Sidekiq Logs</p>
<p>Missing CSRF in System Hooks</p>
<p>Orphaned Upload Files Exposure</p>
<p>Missing Authorization Control API Repository Storage</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/08/28/security-release-gitlab-11-dot-2-dot-2-released/</url>
</references>
<dates>
<discovery>2018-08-28</discovery>
<entry>2018-08-30</entry>
</dates>
</vuln>
<vuln vid="d0be41fe-2a20-4633-b057-4e8b25c41780">
<topic>bro -- array bounds and potential DOS issues</topic>
<affects>
<package>
<name>bro</name>
<range><lt>2.5.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Corelight reports:</p>
<blockquote cite="https://www.bro.org/download/NEWS.bro.html">
<p>Bro 2.5.5 primarily addresses security issues:</p>
<ul>
<li>Fix array bounds checking in BinPAC: for arrays
that are fields within a record, the bounds check
was based on a pointer to the start of the record
rather than the start of the array field, potentially
resulting in a buffer over-read.</li>
<li>Fix SMTP command string comparisons: the number
of bytes compared was based on the user-supplied
string length and can lead to incorrect matches.
e.g. giving a command of "X" incorrectly matched
"X-ANONYMOUSTLS" (and an empty commands match
anything).</li>
</ul>
<p>Address potential vectors for Denial of Service:</p>
<ul>
<li>"Weird" events are now generally suppressed/sampled
by default according to some tunable parameters.</li>
<li>Improved handling of empty lines in several text
protocol analyzers that can cause performance issues
when seen in long sequences.</li>
<li>Add `smtp_excessive_pending_cmds' weird which
serves as a notification for when the "pending
command" queue has reached an upper limit and been
cleared to prevent one from attempting to slowly
exhaust memory.</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://www.bro.org/download/NEWS.bro.html</url>
</references>
<dates>
<discovery>2018-08-28</discovery>
<entry>2018-08-29</entry>
</dates>
</vuln>
<vuln vid="0904e81f-a89d-11e8-afbb-bc5ff4f77b71">
<topic>node.js -- multiple vulnerabilities</topic>
<affects>
<package>
<name>node</name>
<range><lt>10.9.0</lt></range>
</package>
<package>
<name>node8</name>
<range><lt>8.11.4</lt></range>
</package>
<package>
<name>node6</name>
<range><lt>6.14.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Node.js reports:</p>
<blockquote cite="https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/">
<h1>OpenSSL: Client DoS due to large DH parameter</h1>
<p>This fixes a potential denial of service (DoS) attack
against client connections by a malicious server. During a TLS
communication handshake, where both client and server agree to
use a cipher-suite using DH or DHE (Diffie-Hellman, in both
ephemeral and non-ephemeral modes), a malicious server can
send a very large prime value to the client. Because this has
been unbounded in OpenSSL, the client can be forced to spend
an unreasonably long period of time to generate a key,
potentially causing a denial of service.</p>
<h1>OpenSSL: ECDSA key extraction via local side-channel</h1>
<p>Attackers with access to observe cache-timing may be able
to extract DSA or ECDSA private keys by causing the victim to
create several signatures and watching responses. This flaw
does not have a CVE due to OpenSSL policy to not assign itself
CVEs for local-only vulnerabilities that are more academic
than practical. This vulnerability was discovered by Keegan
Ryan at NCC Group and impacts many cryptographic libraries
including OpenSSL.</p>
<h1>Unintentional exposure of uninitialized memory</h1>
<p>Only Node.js 10 is impacted by this flaw.</p>
<p>Node.js TSC member Nikita Skovoroda discovered an argument
processing flaw that causes Buffer.alloc() to return
uninitialized memory. This method is intended to be safe and
only return initialized, or cleared, memory. The third
argument specifying encoding can be passed as a number, this
is misinterpreted by Buffer's internal "fill" method as the
start to a fill operation. This flaw may be abused where
Buffer.alloc() arguments are derived from user input to return
uncleared memory blocks that may contain sensitive
information.</p>
<h1>Out of bounds (OOB) write</h1>
<p>Node.js TSC member Nikita Skovoroda discovered an OOB write
in Buffer that can be used to write to memory outside of a
Buffer's memory space. This can corrupt unrelated Buffer
objects or cause the Node.js process to crash.</p>
<p>When used with UCS-2 encoding (recognized by Node.js under
the names 'ucs2', 'ucs-2', 'utf16le' and 'utf-16le'),
Buffer#write() can be abused to write outside of the bounds of
a single Buffer. Writes that start from the second-to-last
position of a buffer cause a miscalculation of the maximum
length of the input bytes to be written.</p>
</blockquote>
</body>
</description>
<references>
<url>https://nodejs.org/en/blog/vulnerability/august-2018-security-releases/</url>
<cvename>CVE-2018-0732</cvename>
<cvename>CVE-2018-7166</cvename>
<cvename>CVE-2018-12115</cvename>
</references>
<dates>
<discovery>2018-08-16</discovery>
<entry>2018-08-25</entry>
</dates>
</vuln>
<vuln vid="45671c0e-a652-11e8-805b-a4badb2f4699">
<topic>FreeBSD -- Unauthenticated EAPOL-Key Decryption Vulnerability</topic>
<affects>
<package>
<name>FreeBSD</name>
<range><ge>11.2</ge><lt>11.2_2</lt></range>
<range><ge>11.1</ge><lt>11.1_13</lt></range>
<range><ge>10.4</ge><lt>10.4_11</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>When using WPA2, EAPOL-Key frames with the Encrypted
flag and without the MIC flag set, the data field was
decrypted first without verifying the MIC. When the dta
field was encrypted using RC4, for example, when negotiating
TKIP as a pairwise cipher, the unauthenticated but decrypted
data was subsequently processed. This opened wpa_supplicant(8)
to abuse by decryption and recovery of sensitive information
contained in EAPOL-Key messages.</p>
<p>See
https://w1.fi/security/2018-1/unauthenticated-eapol-key-decryption.txt
for a detailed description of the bug.</p>
<h1>Impact:</h1>
<p>All users of the WPA2 TKIP pairwise cipher are vulnerable
to information, for example, the group key.</p>
</body>
</description>
<references>
<cvename>CVE-2018-1452</cvename>
<freebsdsa>SA-18:11.hostapd</freebsdsa>
</references>
<dates>
<discovery>2018-08-14</discovery>
<entry>2018-08-22</entry>
</dates>
</vuln>
<vuln vid="359e1548-a652-11e8-805b-a4badb2f4699">
<topic>FreeBSD -- Resource exhaustion in IP fragment reassembly</topic>
<affects>
<package>
<name>FreeBSD-kernel</name>
<range><ge>11.2</ge><lt>11.2_2</lt></range>
<range><ge>11.1</ge><lt>11.1_13</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>A researcher has notified us of a DoS attack applicable
to another operating system. While FreeBSD may not be
vulnerable to that exact attack, we have identified several
places where inadequate DoS protection could allow an
attacker to consume system resources.</p>
<p>It is not necessary that the attacker be able to establish
two-way communication to carry out these attacks. These
attacks impact both IPv4 and IPv6 fragment reassembly.</p>
<h1>Impact:</h1>
<p>In the worst case, an attacker could send a stream of
crafted fragments with a low packet rate which would consume
a substantial amount of CPU.</p>
<p>Other attack vectors allow an attacker to send a stream
of crafted fragments which could consume a large amount of
CPU or all available mbuf clusters on the system.</p>
<p>These attacks could temporarily render a system unreachable
through network interfaces or temporarily render a system
unresponsive. The effects of the attack should clear within
60 seconds after the attack stops.</p>
</body>
</description>
<references>
<cvename>CVE-2018-6923</cvename>
<freebsdsa>SA-18:10.ip</freebsdsa>
</references>
<dates>
<discovery>2018-08-14</discovery>
<entry>2018-08-22</entry>
</dates>
</vuln>
<vuln vid="2310b814-a652-11e8-805b-a4badb2f4699">
<topic>FreeBSD -- L1 Terminal Fault (L1TF) Kernel Information Disclosure</topic>
<affects>
<package>
<name>FreeBSD-kernel</name>
<range><ge>11.2</ge><lt>11.2_2</lt></range>
<range><ge>11.1</ge><lt>11.1_13</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>On certain Intel 64-bit x86 systems there is a period
of time during terminal fault handling where the CPU may
use speculative execution to try to load data. The CPU may
speculatively access the level 1 data cache (L1D). Data
which would otherwise be protected may then be determined
by using side channel methods.</p>
<p>This issue affects bhyve on FreeBSD/amd64 systems.</p>
<h1>Impact:</h1>
<p>An attacker executing user code, or kernel code inside
of a virtual machine, may be able to read secret data from
the kernel or from another virtual machine.</p>
</body>
</description>
<references>
<cvename>CVE-2018-3620</cvename>
<cvename>CVE-2018-3646</cvename>
<freebsdsa>SA-18:09.l1tf</freebsdsa>
</references>
<dates>
<discovery>2018-08-14</discovery>
<entry>2018-08-22</entry>
</dates>
</vuln>
<vuln vid="e53a908d-a645-11e8-8acd-10c37b4ac2ea">
<topic>gogs -- open redirect vulnerability</topic>
<affects>
<package>
<name>gogs</name>
<range><lt>0.11.53_1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>bluecatli (Tencent's Xuanwu Lab) reports:</p>
<blockquote cite="https://github.com/gogs/gogs/issues/5364">
<p>The function isValidRedirect in gogs/routes/user/auth.go is used in login action to validate if url is on the same site.</p>
<p>If the Location header startswith /\, it will be transformed to // by browsers.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/gogs/gogs/issues/5364</url>
<url>https://github.com/gogs/gogs/pull/5365</url>
<url>https://github.com/gogs/gogs/commit/1f247cf8139cb483276cd8dd06385a800ce9d4b2</url>
</references>
<dates>
<discovery>2018-08-06</discovery>
<entry>2018-08-22</entry>
</dates>
</vuln>
<vuln vid="9e205ef5-a649-11e8-b1f6-6805ca0b3d42">
<topic>phpmyadmin -- XSS in the import dialog</topic>
<affects>
<package>
<name>phpMyAdmin</name>
<name>phpMyAdmin-php56</name>
<name>phpMyAdmin-php70</name>
<name>phpMyAdmin-php71</name>
<name>phpMyAdmin-php72</name>
<range><lt>4.8.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The phpMyAdmin development team reports:</p>
<blockquote cite="https://www.phpmyadmin.net/security/PMASA-2018-5/">
<h3>Description</h3>
<p>A Cross-Site Scripting vulnerability was found in the
file import feature, where an attacker can deliver a payload
to a user through importing a specially-crafted file.</p>
<h3>Severity</h3>
<p>We consider this attack to be of moderate severity.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.phpmyadmin.net/security/PMASA-2018-5/</url>
<cvename>CVE-2018-15605</cvename>
</references>
<dates>
<discovery>2018-08-21</discovery>
<entry>2018-08-22</entry>
</dates>
</vuln>
<vuln vid="fe99d3ca-a63a-11e8-a7c6-54e1ad3d6335">
<topic>libX11 -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>libX11</name>
<range><lt>1.6.6,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The freedesktop.org project reports:</p>
<blockquote cite="https://lists.x.org/archives/xorg-announce/2018-August/002915.html">
<p>The functions XGetFontPath, XListExtensions, and XListFonts are
vulnerable to an off-by-one override on malicious server responses.
The server replies consist of chunks consisting of a length byte
followed by actual string, which is not NUL-terminated.
While parsing the response, the length byte is overridden with '\0',
thus the memory area can be used as storage of C strings later on.
To be able to NUL-terminate the last string, the buffer is reserved
with an additional byte of space. For a boundary check, the variable
chend (end of ch) was introduced, pointing at the end of the buffer
which ch initially points to. Unfortunately there is a difference
in handling "the end of ch". While chend points at the first byte
that must not be written to, the for-loop uses chend as the last
byte that can be written to. Therefore, an off-by-one can occur.</p>
<p>The length value is interpreted as signed char on many systems
(depending on default signedness of char), which can lead to an out
of boundary write up to 128 bytes in front of the allocated storage,
but limited to NUL byte(s).</p>
<p>If the server sends a reply in which even the first string would
overflow the transmitted bytes, list[0] (or flist[0]) will be set to
NULL and a count of 0 is returned. If the resulting list is freed
with XFreeExtensionList or XFreeFontPath later on, the first Xfree
call is turned into Xfree (NULL-1) which will most likely trigger a
segmentation fault. Casting the length value to unsigned char fixes
the problem and allows string values with up to 255 characters.</p>
</blockquote>
</body>
</description>
<references>
<url>https://lists.x.org/archives/xorg-announce/2018-August/002915.html</url>
<cvename>CVE-2018-14598</cvename>
<cvename>CVE-2018-14599</cvename>
<cvename>CVE-2018-14600</cvename>
</references>
<dates>
<discovery>2018-08-21</discovery>
<entry>2018-08-22</entry>
</dates>
</vuln>
<vuln vid="9b19b6df-a4be-11e8-9366-0028f8d09152">
<topic>couchdb -- administrator privilege escalation</topic>
<affects>
<package>
<name>couchdb</name>
<range><lt>2.2.0,2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Apache CouchDB PMC reports:</p>
<blockquote cite="https://lists.apache.org/thread.html/1052ad7a1b32b9756df4f7860f5cb5a96b739f444117325a19a4bf75@%3Cdev.couchdb.apache.org%3E">
<p>Database Administrator could achieve privilege escalation to
the account that CouchDB runs under, by abusing insufficient validation
in the HTTP API, escaping security controls implemented in previous
releases.</p>
</blockquote>
</body>
</description>
<references>
<url>http://docs.couchdb.org/en/stable/cve/2018-11769.html</url>
<cvename>CVE-2018-11769</cvename>
</references>
<dates>
<discovery>2018-06-05</discovery>
<entry>2018-08-08</entry>
</dates>
</vuln>
<vuln vid="7762d7ad-2e38-41d2-9785-c51f653ba8bd">
<topic>botan2 -- ECDSA side channel</topic>
<affects>
<package>
<name>botan2</name>
<range><ge>2.5.0</ge><lt>2.7.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>botan2 developers report:</p>
<blockquote cite="https://botan.randombit.net/security.html#id1">
<p>A side channel in the ECDSA signature operation could allow a local attacker to recover the secret key. Found by Keegan Ryan of NCC Group.</p>
<p>Bug introduced in 2.5.0, fixed in 2.7.0. The 1.10 branch is not affected.</p>
</blockquote>
</body>
</description>
<references>
<url>https://botan.randombit.net/security.html#id1</url>
<url>https://github.com/randombit/botan/pull/1604</url>
<cvename>CVE-2018-12435</cvename>
</references>
<dates>
<discovery>2018-06-13</discovery>
<entry>2018-08-17</entry>
</dates>
</vuln>
<vuln vid="6905f05f-a0c9-11e8-8335-8c164535ad80">
<topic>jenkins -- multiple vulnerabilities</topic>
<affects>
<package>
<name>jenkins</name>
<range><lt>2.138</lt></range>
</package>
<package>
<name>jenkins-lts</name>
<range><lt>2.121.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Jenkins Security Advisory:</p>
<blockquote cite="https://jenkins.io/security/advisory/2018-08-15/">
<h1>Description</h1>
<h5>(Low) SECURITY-637</h5>
<p> Jenkins allowed deserialization of URL objects with host components</p>
<h5>(Medium) SECURITY-672</h5>
<p>Ephemeral user record was created on some invalid authentication attempts</p>
<h5>(Medium) SECURITY-790</h5>
<p>Cron expression form validation could enter infinite loop, potentially resulting in denial of service</p>
<h5>(Low) SECURITY-996</h5>
<p>"Remember me" cookie was evaluated even if that feature is disabled</p>
<h5>(Medium) SECURITY-1071</h5>
<p>Unauthorized users could access agent logs</p>
<h5>(Low) SECURITY-1076</h5>
<p>Unauthorized users could cancel scheduled restarts initiated from the update center</p>
</blockquote>
</body>
</description>
<references>
<url>https://jenkins.io/security/advisory/2018-08-15/</url>
</references>
<dates>
<discovery>2018-08-15</discovery>
<entry>2018-08-15</entry>
</dates>
</vuln>
<vuln vid="98b603c8-9ff3-11e8-ad63-6451062f0f7a">
<topic>Flash Player -- multiple vulnerabilities</topic>
<affects>
<package>
<name>linux-flashplayer</name>
<range><lt>30.0.0.154</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Adobe reports:</p>
<blockquote cite="https://helpx.adobe.com/security/products/flash-player/apsb18-25.html">
<ul>
<li>This update resolves out-of-bounds read vulnerabilities that
could lead to information disclosure (CVE-2018-12824,
CVE-2018-12826, CVE-2018-12827).</li>
<li>This update resolves a security bypass vulnerability that
could lead to security mitigation bypass (CVE-2018-12825).</li>
<li>This update resolves a component vulnerability that
could lead to privilege escalation (CVE-2018-12828).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-12824</cvename>
<cvename>CVE-2018-12825</cvename>
<cvename>CVE-2018-12826</cvename>
<cvename>CVE-2018-12827</cvename>
<cvename>CVE-2018-12828</cvename>
<url>https://helpx.adobe.com/security/products/flash-player/apsb18-25.html</url>
</references>
<dates>
<discovery>2018-08-14</discovery>
<entry>2018-08-14</entry>
</dates>
</vuln>
<vuln vid="c4e9a427-9fc2-11e8-802a-000c29a1e3ec">
<topic>samba -- multiple vulnerabilities</topic>
<affects>
<package>
<name>samba46</name>
<range><lt>4.6.16</lt></range>
</package>
<package>
<name>samba47</name>
<range><lt>4.7.9</lt></range>
</package>
<package>
<name>samba48</name>
<range><lt>4.8.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The samba project reports:</p>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-1139.html">
<p>Samba releases 4.7.0 to 4.8.3 (inclusive) contain an error which
allows authentication using NTLMv1 over an SMB1 transport (either
directory or via NETLOGON SamLogon calls from a member server), even
when NTLMv1 is explicitly disabled on the server.</p>
</blockquote>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-1140.html">
<p>Missing input sanitization checks on some of the input parameters to
LDB database layer cause the LDAP server and DNS server to crash when
following a NULL pointer.</p>
</blockquote>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-10858.html">
<p>Samba releases 3.2.0 to 4.8.3 (inclusive) contain an error in
libsmbclient that could allow a malicious server to overwrite
client heap memory by returning an extra long filename in a directory
listing.</p>
</blockquote>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-10918.html">
<p>Missing database output checks on the returned directory attributes
from the LDB database layer cause the DsCrackNames call in the DRSUAPI
server to crash when following a NULL pointer.</p>
</blockquote>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-10919.html">
<p>All versions of the Samba Active Directory LDAP server from 4.0.0
onwards are vulnerable to the disclosure of confidential attribute
values, both of attributes where the schema SEARCH_FLAG_CONFIDENTIAL
(0x80) searchFlags bit and where an explicit Access Control Entry has
been specified on the ntSecurityDescriptor.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.samba.org/samba/security/CVE-2018-1139.html</url>
<cvename>CVE-2018-1139</cvename>
<url>https://www.samba.org/samba/security/CVE-2018-1140.html</url>
<cvename>CVE-2018-1140</cvename>
<url>https://www.samba.org/samba/security/CVE-2018-10858.html</url>
<cvename>CVE-2018-10858</cvename>
<url>https://www.samba.org/samba/security/CVE-2018-10918.html</url>
<cvename>CVE-2018-10918</cvename>
<url>https://www.samba.org/samba/security/CVE-2018-10919.html</url>
<cvename>CVE-2018-10919</cvename>
</references>
<dates>
<discovery>2018-08-14</discovery>
<entry>2018-08-14</entry>
</dates>
</vuln>
<vuln vid="e714b7d2-39f6-4992-9f48-e6b2f5f949df">
<topic>GraphicsMagick -- SVG/Rendering vulnerability</topic>
<affects>
<package>
<name>GraphicsMagick</name>
<range><lt>1.3.30,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GraphicsMagick News:</p>
<blockquote cite="http://www.graphicsmagick.org/NEWS.html">
<p>Fix heap write overflow of PrimitiveInfo and PointInfo arrays. This is
another manefestation of CVE-2016-2317, which should finally be fixed
correctly due to active detection/correction of pending overflow rather
than using estimation.</p>
</blockquote>
</body>
</description>
<references>
<url>http://www.graphicsmagick.org/NEWS.html</url>
<cvename>CVE-2016-2317</cvename>
</references>
<dates>
<discovery>2018-06-23</discovery>
<entry>2018-08-11</entry>
</dates>
</vuln>
<vuln vid="5a771686-9e33-11e8-8b2d-9cf7a8059466">
<topic>chicken -- multiple vulnerabilities</topic>
<affects>
<package>
<name>chicken</name>
<range><lt>4.13.0,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>CHICKEN reports:</p>
<blockquote cite="https://code.call-cc.org/releases/4.13.0/NEWS">
<ul>
<li>CVE-2017-6949: Unchecked malloc() call in SRFI-4
constructors when allocating in non-GC memory, resulting
in potential 1-word buffer overrun and/or segfault</li>
<li>CVE-2017-9334: "length" crashes on improper lists</li>
<li>CVE-2017-11343: The randomization factor of the symbol
table was set before the random seed was set, causing it
to have a fixed value on many platforms</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://code.call-cc.org/releases/4.13.0/NEWS</url>
<cvename>CVE-2017-6949</cvename>
<cvename>CVE-2017-9334</cvename>
<cvename>CVE-2017-11343</cvename>
</references>
<dates>
<discovery>2017-03-16</discovery>
<entry>2018-08-12</entry>
</dates>
</vuln>
<vuln vid="bcf56a42-9df8-11e8-afb0-589cfc0f81b0">
<topic>gitea -- TOTP passcode reuse</topic>
<affects>
<package>
<name>gitea</name>
<range><lt>1.5.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Gitea project reports:</p>
<blockquote cite="https://blog.gitea.io/2018/08/gitea-1.5.0-is-released/">
<p>TOTP passcodes can be reused.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/go-gitea/gitea/pull/3878</url>
</references>
<dates>
<discovery>2018-05-01</discovery>
<entry>2018-08-12</entry>
</dates>
</vuln>
<vuln vid="f4876dd4-9ca8-11e8-aa17-0011d823eebd">
<topic>mbed TLS -- plaintext recovery vulnerabilities</topic>
<affects>
<package>
<name>mbedtls</name>
<range><lt>2.12</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Simon Butcher reports:</p>
<blockquote cite="https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2018-02">
<ul>
<li>When using a CBC based ciphersuite, a remote attacker can
partially recover the plaintext.</li>
<li>When using a CBC based ciphersuite, an attacker with the
ability to execute arbitrary code on the machine under attack
can partially recover the plaintext by use of cache based
side-channels.</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2018-02</url>
<cvename>CVE-2018-0497</cvename>
<cvename>CVE-2018-0498</cvename>
</references>
<dates>
<discovery>2018-07-24</discovery>
<entry>2018-08-10</entry>
</dates>
</vuln>
<vuln vid="96eab874-9c79-11e8-b34b-6cc21735f730">
<topic>PostgreSQL -- two vulnerabilities</topic>
<affects>
<package>
<name>postgresql10-server</name>
<range><lt>10.5</lt></range>
</package>
<package>
<name>postgresql96-server</name>
<range><lt>9.6.10</lt></range>
</package>
<package>
<name>postgresql95-server</name>
<range><lt>9.5.14</lt></range>
</package>
<package>
<name>postgresql94-server</name>
<range><lt>9.4.19</lt></range>
</package>
<package>
<name>postgresql93-server</name>
<range><lt>9.3.24</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The PostgreSQL project reports:</p>
<blockquote cite="https://www.postgresql.org/about/news/1878/">
<p>CVE-2018-10915: Certain host connection parameters defeat
client-side security defenses</p>
<p>libpq, the client connection API for PostgreSQL that is also used
by other connection libraries, had an internal issue where it did not
reset all of its connection state variables when attempting to
reconnect. In particular, the state variable that determined whether
or not a password is needed for a connection would not be reset, which
could allow users of features requiring libpq, such as the "dblink" or
"postgres_fdw" extensions, to login to servers they should not be able
to access.</p>
<p>CVE-2018-10925: Memory disclosure and missing authorization in
`INSERT ... ON CONFLICT DO UPDATE`</p>
<p>An attacker able to issue CREATE TABLE can read arbitrary bytes of
server memory using an upsert (`INSERT ... ON CONFLICT DO UPDATE`)
query. By default, any user can exploit that. A user that has
specific INSERT privileges and an UPDATE privilege on at least one
column in a given table can also update other columns using a view and
an upsert query.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.postgresql.org/about/news/1878/</url>
<cvename>CVE-2018-10915</cvename>
<cvename>CVE-2018-10925</cvename>
</references>
<dates>
<discovery>2018-08-09</discovery>
<entry>2018-08-10</entry>
</dates>
</vuln>
<vuln vid="909be51b-9b3b-11e8-add2-b499baebfeaf">
<topic>MySQL -- multiple vulnerabilities</topic>
<affects>
<package>
<name>mariadb55-server</name>
<range><lt>5.5.61</lt></range>
</package>
<package>
<name>mariadb100-server</name>
<range><lt>10.0.36</lt></range>
</package>
<package>
<name>mariadb101-server</name>
<range><lt>10.1.35</lt></range>
</package>
<package>
<name>mariadb102-server</name>
<range><lt>10.2.17</lt></range>
</package>
<package>
<name>mariadb103-server</name>
<range><lt>10.3.9</lt></range>
</package>
<package>
<name>mysql55-server</name>
<range><lt>5.5.61</lt></range>
</package>
<package>
<name>mysql56-server</name>
<range><lt>5.6.41</lt></range>
</package>
<package>
<name>mysql57-server</name>
<range><lt>5.7.23</lt></range>
</package>
<package>
<name>mysql80-server</name>
<range><lt>8.0.12</lt></range>
</package>
<package>
<name>percona55-server</name>
<range><lt>5.5.61</lt></range>
</package>
<package>
<name>percona56-server</name>
<range><lt>5.6.41</lt></range>
</package>
<package>
<name>percona57-server</name>
<range><lt>5.7.23</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Oracle reports:</p>
<blockquote cite="http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html">
<p>Multiple vulnerabilities have been disclosed by Oracle without
further detail. CVSS scores 7.1 - 2.7</p>
</blockquote>
</body>
</description>
<references>
<url>http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html</url>
<cvename>CVE-2018-3064</cvename>
<cvename>CVE-2018-0739</cvename>
<cvename>CVE-2018-3070</cvename>
<cvename>CVE-2018-3060</cvename>
<cvename>CVE-2018-3065</cvename>
<cvename>CVE-2018-3073</cvename>
<cvename>CVE-2018-3074</cvename>
<cvename>CVE-2018-3081</cvename>
<cvename>CVE-2018-3071</cvename>
<cvename>CVE-2018-3079</cvename>
<cvename>CVE-2018-3054</cvename>
<cvename>CVE-2018-3077</cvename>
<cvename>CVE-2018-3078</cvename>
<cvename>CVE-2018-3080</cvename>
<cvename>CVE-2018-3061</cvename>
<cvename>CVE-2018-3067</cvename>
<cvename>CVE-2018-3063</cvename>
<cvename>CVE-2018-3075</cvename>
<cvename>CVE-2018-3058</cvename>
<cvename>CVE-2018-3056</cvename>
<cvename>CVE-2018-3066</cvename>
<cvename>CVE-2018-2767</cvename>
<cvename>CVE-2018-3084</cvename>
<cvename>CVE-2018-3082</cvename>
</references>
<dates>
<discovery>2018-07-17</discovery>
<entry>2018-08-08</entry>
</dates>
</vuln>
<vuln vid="5786185a-9a43-11e8-b34b-6cc21735f730">
<topic>xml-security-c -- crashes on malformed KeyInfo content</topic>
<affects>
<package>
<name>apache-xml-security-c</name>
<range><lt>2.0.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The shibboleth project reports:</p>
<blockquote cite="https://shibboleth.net/community/advisories/secadv_20180803.txt">
<p>
SAML messages, assertions, and metadata all commonly make use of the
XML Signature KeyInfo construct, which expresses information about
keys and certificates used in signing or encrypting XML.
</p>
<p>
The Apache Santuario XML Security for C++ library contained code
paths at risk of dereferencing null pointers when processing various
kinds of malformed KeyInfo hints typically found in signed or
encrypted XML. The usual effect is a crash, and in the case of the
Shibboleth SP software, a crash in the shibd daemon, which prevents
access to protected resources until the daemon is restarted.
</p>
</blockquote>
</body>
</description>
<references>
<url>https://shibboleth.net/community/advisories/secadv_20180803.txt</url>
</references>
<dates>
<discovery>2018-08-03</discovery>
<entry>2018-08-07</entry>
</dates>
</vuln>
<vuln vid="3c2eea8c-99bf-11e8-8bee-a4badb2f4699">
<topic>FreeBSD -- Resource exhaustion in TCP reassembly</topic>
<affects>
<package>
<name>FreeBSD-kernel</name>
<range><ge>11.2</ge><lt>11.2_1</lt></range>
<range><ge>11.1</ge><lt>11.1_12</lt></range>
<range><ge>10.4</ge><lt>10.4_10</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>One of the data structures that holds TCP segments uses
an inefficient algorithm to reassemble the data. This causes
the CPU time spent on segment processing to grow linearly
with the number of segments in the reassembly queue.</p>
<h1>Impact:</h1>
<p>An attacker who has the ability to send TCP traffic to
a victim system can degrade the victim system's network
performance and/or consume excessive CPU by exploiting the
inefficiency of TCP reassembly handling, with relatively
small bandwidth cost.</p>
</body>
</description>
<references>
<cvename>CVE-2018-6922</cvename>
<freebsdsa>SA-18:08.tcp</freebsdsa>
</references>
<dates>
<discovery>2018-08-06</discovery>
<entry>2018-08-06</entry>
</dates>
</vuln>
<vuln vid="9e2d0dcf-9926-11e8-a92d-0050562a4d7b">
<topic>py-cryptography -- tag forgery vulnerability</topic>
<affects>
<package>
<name>py27-cryptography</name>
<name>py34-cryptography</name>
<name>py35-cryptography</name>
<name>py36-cryptography</name>
<name>py37-cryptography</name>
<range><lt>2.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Python Cryptographic Authority (PyCA) project reports:</p>
<blockquote cite="https://cryptography.io/en/latest/changelog/#v2-3">
<p>finalize_with_tag() allowed tag truncation by default which can allow tag forgery in some cases. The method now enforces the min_tag_length provided to the GCM constructor</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-10903</cvename>
</references>
<dates>
<discovery>2018-07-17</discovery>
<entry>2018-08-06</entry>
</dates>
</vuln>
<vuln vid="06c4a79b-981d-11e8-b460-9c5c8e75236a">
<topic>cgit -- directory traversal vulnerability</topic>
<affects>
<package>
<name>cgit</name>
<range><lt>1.2.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Jann Horn reports:</p>
<blockquote cite="https://lists.zx2c4.com/pipermail/cgit/2018-August/004176.html">
<p>cgit_clone_objects in CGit before 1.2.1 has a directory traversal vulnerability when `enable-http-clone=1` is not turned off, as demonstrated by a cgit/cgit.cgi/git/objects/?path=../ request.</p>
</blockquote>
</body>
</description>
<references>
<url>https://lists.zx2c4.com/pipermail/cgit/2018-August/004176.html</url>
<cvename>CVE-2018-14912</cvename>
</references>
<dates>
<discovery>2018-08-03</discovery>
<entry>2018-08-04</entry>
</dates>
</vuln>
<vuln vid="e309a2c7-598b-4fa6-a398-bc72fbd1d167">
<topic>rubygem-doorkeeper -- token revocation vulnerability</topic>
<affects>
<package>
<name>rubygem-doorkeeper</name>
<name>rubygem-doorkeeper43</name>
<name>rubygem-doorkeeper-rails5</name>
<name>rubygem-doorkeeper-rails50</name>
<range><lt>4.4.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>NVD reports:</p>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2018-1000211">
<p>Doorkeeper version 4.2.0 and later contains a Incorrect Access Control
vulnerability in Token revocation API's authorized method that can
result in Access tokens are not revoked for public OAuth apps, leaking
access until expiry.</p>
</blockquote>
</body>
</description>
<references>
<url>https://nvd.nist.gov/vuln/detail/CVE-2018-1000211</url>
<url>https://github.com/doorkeeper-gem/doorkeeper/pull/1120</url>
<cvename>CVE-2018-1000211</cvename>
</references>
<dates>
<discovery>2018-07-13</discovery>
<entry>2018-07-31</entry>
<modified>2018-08-03</modified>
</dates>
</vuln>
<vuln vid="ca05d9da-ac1d-4113-8a05-ffe9cd0d6160">
<topic>sinatra -- XSS vulnerability</topic>
<affects>
<package>
<name>rubygem-sinatra</name>
<range><ge>2.0.0</ge><lt>2.0.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Sinatra blog:</p>
<blockquote cite="http://sinatrarb.com/2018/06/09/sinatra-2.0.2-and-2.0.3.html">
<p>Sinatra had a critical vulnerability since v2.0.0. The purpose of this
release is to fix CVE-2018-11627.</p>
<p>The vulnerability is that XSS can be executed by using illegal parameters.</p>
</blockquote>
</body>
</description>
<references>
<url>http://sinatrarb.com/2018/06/09/sinatra-2.0.2-and-2.0.3.html</url>
<url>https://github.com/sinatra/sinatra/blob/master/CHANGELOG.md</url>
<cvename>CVE-2018-11627</cvename>
</references>
<dates>
<discovery>2018-06-09</discovery>
<entry>2018-07-31</entry>
</dates>
</vuln>
<vuln vid="b4f0ad36-94a5-11e8-9007-080027ac955c">
<topic>mailman -- content spoofing with invalid list names in web UI</topic>
<affects>
<package><name>mailman</name> <range><lt>2.1.28</lt></range></package>
<package><name>mailman-with-htdig</name><range><lt>2.1.28</lt></range></package>
<package><name>ja-mailman</name> <range><lt>2.1.14.j7_6,1</lt></range></package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mark Sapiro reports:</p>
<blockquote cite="https://bugs.launchpad.net/mailman/+bug/1780874">
<p>A URL with a very long text listname such as</p>
<pre>http://www.example.com/mailman/listinfo/This_is_a_long_string_with_some_phishing_text</pre>
<p>will echo the text in the "No such list" error response. This can be used to make a potential victim think the phishing text comes from a trusted site.</p>
<p>This issue was discovered by Hammad Qureshi.</p>
</blockquote>
</body>
</description>
<references>
<url>https://bugs.launchpad.net/mailman/+bug/1780874</url>
<url>https://mail.python.org/pipermail/mailman-announce/2018-July/000241.html</url>
<cvename>CVE-2018-13796</cvename>
</references>
<dates>
<discovery>2018-07-09</discovery>
<entry>2018-07-31</entry>
</dates>
</vuln>
<vuln vid="0822a4cf-9318-11e8-8d88-00e04c1ea73d">
<topic>mantis -- multiple vulnerabilities</topic>
<affects>
<package>
<name>mantis</name>
<range><lt>2.15.0,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>mantis reports:</p>
<blockquote cite="https://github.com/mantisbt/mantisbt/commit/8b5fa243dbf04344a55fe880135ec149fc1f439f">
<p>Teun Beijers reported a cross-site scripting (XSS) vulnerability in
the Edit Filter page which allows execution of arbitrary code
(if CSP settings permit it) when displaying a filter with a crafted
name. Prevent the attack by sanitizing the filter name before display.</p>
<p>Ömer Cıtak, Security Researcher at Netsparker, reported this
vulnerability, allowing remote attackers to inject arbitrary code
(if CSP settings permit it) through a crafted PATH_INFO on
view_filters_page.php. Prevent the attack by sanitizing the output
of $_SERVER['PHP_SELF'] before display.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/mantisbt/mantisbt/commit/8b5fa243dbf04344a55fe880135ec149fc1f439f</url>
<url>https://github.com/mantisbt/mantisbt/commit/4efac90ed89a5c009108b641e2e95683791a165a</url>
<cvename>CVE-2018-14504</cvename>
<cvename>CVE-2018-13066</cvename>
</references>
<dates>
<discovery>2018-07-13</discovery>
<entry>2018-07-29</entry>
<modified>2018-08-24</modified>
</dates>
</vuln>
<vuln vid="e97a8852-32dd-4291-ba4d-92711daff056">
<topic>py-bleach -- unsanitized character entities</topic>
<affects>
<package>
<name>py27-bleach</name>
<name>py36-bleach</name>
<range><ge>2.1.0</ge><lt>2.1.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>bleach developer reports:</p>
<blockquote cite="https://github.com/mozilla/bleach/blob/v2.1.3/CHANGES">
<p>Attributes that have URI values weren't properly sanitized if the
values contained character entities. Using character entities, it
was possible to construct a URI value with a scheme that was not
allowed that would slide through unsanitized.</p>
<p>This security issue was introduced in Bleach 2.1. Anyone using
Bleach 2.1 is highly encouraged to upgrade.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/mozilla/bleach/blob/v2.1.3/CHANGES</url>
</references>
<dates>
<discovery>2018-03-05</discovery>
<entry>2018-07-27</entry>
</dates>
</vuln>
<vuln vid="07d04eef-d8e2-11e6-a071-001e67f15f5a">
<topic>lshell -- Shell autocomplete reveals forbidden directories</topic>
<affects>
<package>
<name>lshell</name>
<range><lt>0.9.18</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>lshell reports:</p>
<blockquote cite="https://github.com/ghantoos/lshell/issues/151">
<p>The autocomplete feature allows users to list directories, while they do not have access to those paths (issue #109).</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/ghantoos/lshell/issues/109</url>
</references>
<dates>
<discovery>2015-07-25</discovery>
<entry>2018-07-27</entry>
</dates>
</vuln>
<vuln vid="f353525a-d8b8-11e6-a071-001e67f15f5a">
<topic>lshell -- Multiple security issues</topic>
<affects>
<package>
<name>lshell</name>
<range><le>0.9.18</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>lshell reports:</p>
<blockquote cite="https://github.com/ghantoos/lshell/issues/151">
<p>It is possible to escape lshell if an allowed command can execute an arbitrary non allowed one (issue #122).</p>
<p>Inappropriate parsing of commands can lead to arbitrary command execution (issue #147, #149, #151).</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/ghantoos/lshell/issues/122</url>
<url>https://github.com/ghantoos/lshell/issues/147</url>
<url>https://github.com/ghantoos/lshell/issues/149</url>
<url>https://github.com/ghantoos/lshell/issues/151</url>
</references>
<dates>
<discovery>2016-02-04</discovery>
<entry>2018-07-27</entry>
</dates>
</vuln>
<vuln vid="11dc3890-0e64-11e8-99b0-d017c2987f9a">
<topic>OpenJPEG -- multiple vulnerabilities</topic>
<affects>
<package>
<name>openjpeg</name>
<range><lt>2.3.0_3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>OpenJPEG reports:</p>
<blockquote cite="https://github.com/uclouvain/openjpeg/issues?q=is%3Aissue+CVE-2017-17479+OR+CVE-2017-17480+OR+CVE-2018-5785+OR+CVE-2018-6616">
<p>Multiple vulnerabilities have been found in OpenJPEG, the
opensource JPEG 2000 codec. Please consult the CVE list for further
details.</p>
<p>CVE-2017-17479 and CVE-2017-17480 were fixed in r477112.</p>
<p>CVE-2018-5785 was fixed in r480624.</p>
<p>CVE-2018-6616 was fixed in r489415.</p>
</blockquote>
</body>
</description>
<references>
<url>https://nvd.nist.gov/vuln/detail/CVE-2017-17479</url>
<url>https://nvd.nist.gov/vuln/detail/CVE-2017-17480</url>
<url>https://nvd.nist.gov/vuln/detail/CVE-2018-5785</url>
<url>https://nvd.nist.gov/vuln/detail/CVE-2018-6616</url>
<cvename>CVE-2017-17479</cvename>
<cvename>CVE-2017-17480</cvename>
<cvename>CVE-2018-5785</cvename>
<cvename>CVE-2018-6616</cvename>
</references>
<dates>
<discovery>2017-12-08</discovery>
<entry>2018-07-27</entry>
<modified>2019-02-11</modified>
</dates>
</vuln>
<vuln vid="5ccbb2f8-c798-11e7-a633-009c02a2ab30">
<topic>ffmpeg -- multiple vulnerabilities</topic>
<affects>
<package>
<name>ffmpeg</name>
<range><lt>3.3.5_1,1</lt></range>
<range><ge>3.4,1</ge><le>3.4.1_4,1</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>MITRE reports:</p>
<blockquote cite="http://ffmpeg.org/security.html">
<p>Multiple vulnerabilities have been found in FFmpeg. Please refer
to CVE list for details.</p>
<p>Note: CVE-2017-15186 and CVE-2017-15672 affect only the 3.3 branch
before 3.3.5, CVE-2017-16840 and CVE-2017-17081 have been fixed
in 3.4.1. They're listed here for completeness of the record.</p>
</blockquote>
</body>
</description>
<references>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15186</url>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15672</url>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16840</url>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17081</url>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6392</url>
<url>http://ffmpeg.org/security.html</url>
<cvename>CVE-2017-15186</cvename>
<cvename>CVE-2017-15672</cvename>
<cvename>CVE-2017-16840</cvename>
<cvename>CVE-2017-17081</cvename>
<cvename>CVE-2018-6392</cvename>
</references>
<dates>
<discovery>2017-10-09</discovery>
<entry>2018-07-27</entry>
</dates>
</vuln>
<vuln vid="bfda2d80-0858-11e8-ad5c-0021ccb9e74d">
<topic>GIMP - Heap Buffer Overflow Vulnerability</topic>
<affects>
<package>
<name>gimp</name>
<range><lt>2.8.22,2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GNOME reports:</p>
<blockquote cite="https://www.securityfocus.com/bid/102765/references">
<p>CVE-2017-17786 Out of bounds read / heap overflow in tga importer / function bgr2rgb.part.1</p>
</blockquote>
</body>
</description>
<references>
<url>https://bugzilla.gnome.org/show_bug.cgi?id=739134</url>
<cvename>CVE-2017-17786</cvename>
</references>
<dates>
<discovery>2017-12-21</discovery>
<entry>2018-07-27</entry>
</dates>
</vuln>
<vuln vid="b9c525d9-9198-11e8-beba-080027ef1a23">
<topic>chromium -- multiple vulnerabilities</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>68.0.3440.75</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html">
<p>42 security fixes in this release, including:</p>
<ul>
<li>[850350] High CVE-2018-6153: Stack buffer overflow in Skia. Reported by Zhen Zhou of NSFOCUS Security Team on 2018-06-07</li>
<li>[848914] High CVE-2018-6154: Heap buffer overflow in WebGL. Reported by Omair on 2018-06-01</li>
<li>[842265] High CVE-2018-6155: Use after free in WebRTC. Reported by Natalie Silvanovich of Google Project Zero on 2018-05-11</li>
<li>[841962] High CVE-2018-6156: Heap buffer overflow in WebRTC. Reported by Natalie Silvanovich of Google Project Zero on 2018-05-10</li>
<li>[840536] High CVE-2018-6157: Type confusion in WebRTC. Reported by Natalie Silvanovich of Google Project Zero on 2018-05-07</li>
<li>[812667] Medium CVE-2018-6150: Cross origin information disclosure in Service Workers. Reported by Rob Wu on 2018-02-15</li>
<li>[805905] Medium CVE-2018-6151: Bad cast in DevTools. Reported by Rob Wu on 2018-01-25</li>
<li>[805445] Medium CVE-2018-6152: Local file write in DevTools. Reported by Rob Wu on 2018-01-24</li>
<li>[841280] Medium CVE-2018-6158: Use after free in Blink. Reported by Zhe Jin, Luyao Liu from Chengdu Security Response Center of Qihoo 360 Technology Co. Ltd on 2018-05-09</li>
<li>[837275] Medium CVE-2018-6159: Same origin policy bypass in ServiceWorker. Reported by Jun Kokatsu (@shhnjk) on 2018-04-26</li>
<li>[839822] Medium CVE-2018-6160: URL spoof in Chrome on iOS. Reported by evi1m0 of Bilibili Security Team on 2018-05-04</li>
<li>[826552] Medium CVE-2018-6161: Same origin policy bypass in WebAudio. Reported by Jun Kokatsu (@shhnjk) on 2018-03-27</li>
<li>[804123] Medium CVE-2018-6162: Heap buffer overflow in WebGL. Reported by Omair on 2018-01-21</li>
<li>[849398] Medium CVE-2018-6163: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-06-04</li>
<li>[848786] Medium CVE-2018-6164: Same origin policy bypass in ServiceWorker. Reported by Jun Kokatsu (@shhnjk) on 2018-06-01</li>
<li>[847718] Medium CVE-2018-6165: URL spoof in Omnibox. Reported by evi1m0 of Bilibili Security Team on 2018-05-30</li>
<li>[835554] Medium CVE-2018-6166: URL spoof in Omnibox. Reported by Lnyas Zhang on 2018-04-21</li>
<li>[833143] Medium CVE-2018-6167: URL spoof in Omnibox. Reported by Lnyas Zhang on 2018-04-15</li>
<li>[828265] Medium CVE-2018-6168: CORS bypass in Blink. Reported by Gunes Acar and Danny Y. Huang of Princeton University, Frank Li of UC Berkeley on 2018-04-03</li>
<li>[394518] Medium CVE-2018-6169: Permissions bypass in extension installation. Reported by Sam P on 2014-07-16</li>
<li>[862059] Medium CVE-2018-6170: Type confusion in PDFium. Reported by Anonymous on 2018-07-10</li>
<li>[851799] Medium CVE-2018-6171: Use after free in WebBluetooth. Reported by amazon@mimetics.ca on 2018-06-12</li>
<li>[847242] Medium CVE-2018-6172: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-05-28</li>
<li>[836885] Medium CVE-2018-6173: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-04-25</li>
<li>[835299] Medium CVE-2018-6174: Integer overflow in SwiftShader. Reported by Mark Brand of Google Project Zero on 2018-04-20</li>
<li>[826019] Medium CVE-2018-6175: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-03-26</li>
<li>[666824] Medium CVE-2018-6176: Local user privilege escalation in Extensions. Reported by Jann Horn of Google Project Zero on 2016-11-18</li>
<li>[826187] Low CVE-2018-6177: Cross origin information leak in Blink. Reported by Ron Masas (Imperva) on 2018-03-27</li>
<li>[823194] Low CVE-2018-6178: UI spoof in Extensions. Reported by Khalil Zhani on 2018-03-19</li>
<li>[816685] Low CVE-2018-6179: Local file information leak in Extensions. Reported by Anonymous on 2018-02-26</li>
<li>[797461] Low CVE-2018-6044: Request privilege escalation in Extensions. Reported by Wob Wu on 2017-12-23</li>
<li>[791324] Low CVE-2018-4117: Cross origin information leak in Blink. Reported by AhsanEjaz - @AhsanEjazA on 2017-12-03</li>
<li>[866821] Various fixes from internal audits, fuzzing and other initiatives</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-4117</cvename>
<cvename>CVE-2018-6044</cvename>
<cvename>CVE-2018-6150</cvename>
<cvename>CVE-2018-6151</cvename>
<cvename>CVE-2018-6152</cvename>
<cvename>CVE-2018-6153</cvename>
<cvename>CVE-2018-6154</cvename>
<cvename>CVE-2018-6155</cvename>
<cvename>CVE-2018-6156</cvename>
<cvename>CVE-2018-6157</cvename>
<cvename>CVE-2018-6158</cvename>
<cvename>CVE-2018-6159</cvename>
<cvename>CVE-2018-6160</cvename>
<cvename>CVE-2018-6161</cvename>
<cvename>CVE-2018-6162</cvename>
<cvename>CVE-2018-6163</cvename>
<cvename>CVE-2018-6164</cvename>
<cvename>CVE-2018-6165</cvename>
<cvename>CVE-2018-6166</cvename>
<cvename>CVE-2018-6167</cvename>
<cvename>CVE-2018-6168</cvename>
<cvename>CVE-2018-6169</cvename>
<cvename>CVE-2018-6170</cvename>
<cvename>CVE-2018-6171</cvename>
<cvename>CVE-2018-6172</cvename>
<cvename>CVE-2018-6173</cvename>
<cvename>CVE-2018-6174</cvename>
<cvename>CVE-2018-6175</cvename>
<cvename>CVE-2018-6176</cvename>
<cvename>CVE-2018-6177</cvename>
<cvename>CVE-2018-6178</cvename>
<cvename>CVE-2018-6179</cvename>
<url>https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html</url>
</references>
<dates>
<discovery>2018-07-24</discovery>
<entry>2018-07-27</entry>
</dates>
</vuln>
<vuln vid="3849e28f-8693-11e8-9610-9c5c8e75236a">
<topic>curl -- SMTP send heap buffer overflow</topic>
<affects>
<package>
<name>curl</name>
<range><ge>7.54.1</ge><lt>7.61.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Peter Wu reports:</p>
<blockquote cite="https://curl.haxx.se/docs/adv_2018-70a2.html">
<p>curl might overflow a heap based memory buffer when sending data over SMTP and using a reduced read buffer.</p>
</blockquote>
</body>
</description>
<references>
<url>https://curl.haxx.se/docs/adv_2018-70a2.html</url>
<cvename>CVE-2018-0500</cvename>
</references>
<dates>
<discovery>2018-07-11</discovery>
<entry>2018-07-27</entry>
<modified>2018-07-28</modified>
</dates>
</vuln>
<vuln vid="2da838f9-9168-11e8-8c75-d8cb8abf62dd">
<topic>Gitlab -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>11.1.0</ge><lt>11.1.2</lt></range>
<range><ge>11.0.0</ge><lt>11.0.5</lt></range>
<range><ge>2.7.0</ge><lt>10.8.7</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/07/26/security-release-gitlab-11-dot-1-dot-2-released/">
<p>Markdown DoS</p>
<p>Information Disclosure Prometheus Metrics</p>
<p>CSRF in System Hooks</p>
<p>Persistent XSS Pipeline Tooltip</p>
<p>Persistent XSS in Branch Name via Web IDE</p>
<p>Persistent XSS in Branch Name via Web IDE</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-14601</cvename>
<cvename>CVE-2018-14602</cvename>
<cvename>CVE-2018-14603</cvename>
<cvename>CVE-2018-14604</cvename>
<cvename>CVE-2018-14605</cvename>
<cvename>CVE-2018-14606</cvename>
<url>https://about.gitlab.com/2018/07/26/security-release-gitlab-11-dot-1-dot-2-released/</url>
</references>
<dates>
<discovery>2018-07-26</discovery>
<entry>2018-07-27</entry>
</dates>
</vuln>
<vuln vid="38fec4bd-90f7-11e8-aafb-1c39475b9f84">
<topic>Fix a buffer overflow in the tiff reader</topic>
<affects>
<package>
<name>vips</name>
<range><lt>8.6.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>libvips reports:</p>
<blockquote cite="https://github.com/jcupitt/libvips/releases/tag/v8.6.5">
<p>A buffer overflow was found and fixed in the libvips code</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/jcupitt/libvips/releases/tag/v8.6.5</url>
</references>
<dates>
<discovery>2018-07-22</discovery>
<entry>2018-07-26</entry>
</dates>
</vuln>
<vuln vid="efe43d2b-8f35-11e8-b9e8-dcfe074bd614">
<topic>Memory leak in different components</topic>
<affects>
<package>
<name>libsixel</name>
<range><lt>1.8.2,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>MITRE reports:</p>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2018-14072">
<p>bsixel 1.8.1 has a memory leak in sixel_decoder_decode in
decoder.c, image_buffer_resize in fromsixel.c, sixel_decode_raw in
fromsixel.c and sixel_allocator_new in allocator.c</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-14072</cvename>
<cvename>CVE-2018-14073</cvename>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14072</url>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14073</url>
</references>
<dates>
<discovery>2018-07-15</discovery>
<entry>2018-07-24</entry>
</dates>
</vuln>
<vuln vid="dc57ad48-ecbb-439b-a4d0-5869be47684e">
<topic>vlc -- Use after free vulnerability</topic>
<affects>
<package>
<name>vlc</name>
<range><le>2.2.8_6,4</le></range>
</package>
<package>
<name>vlc-qt4</name>
<range><le>2.2.8_6,4</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mitre reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11529">
<p>VideoLAN VLC media player 2.2.x is prone to a use after free
vulnerability which an attacker can leverage to execute arbitrary
code via crafted MKV files. Failed exploit attempts will likely
result in denial of service conditions.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-11529</cvename>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11529</url>
<url>http://seclists.org/fulldisclosure/2018/Jul/28</url>
<url>https://github.com/rapid7/metasploit-framework/pull/10335</url>
<url>https://github.com/videolan/vlc-3.0/commit/c472668ff873cfe29281822b4548715fb7bb0368</url>
<url>https://github.com/videolan/vlc-3.0/commit/d2dadb37e7acc25ae08df71e563855d6e17b5b42</url>
</references>
<dates>
<discovery>2018-06-06</discovery>
<entry>2018-07-21</entry>
</dates>
</vuln>
<vuln vid="a2f35081-8a02-11e8-8fa5-4437e6ad11c4">
<topic>mutt -- remote code injection and path traversal vulnerability</topic>
<affects>
<package>
<name>mutt</name>
<range><lt>1.10.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Kevin J. McCarthy reports:</p>
<blockquote cite="http://lists.mutt.org/pipermail/mutt-announce/Week-of-Mon-20180716/000004.html">
<p>Fixes a remote code injection vulnerability when "subscribing"
to an IMAP mailbox, either via $imap_check_subscribed, or via the
<subscribe> function in the browser menu. Mutt was generating a
"mailboxes" command and sending that along to the muttrc parser.
However, it was not escaping "`", which executes code and inserts
the result. This would allow a malicious IMAP server to execute
arbitrary code (for $imap_check_subscribed).</p>
<p>Fixes POP body caching path traversal vulnerability.</p>
<p>Fixes IMAP header caching path traversal vulnerability.</p>
<p>CVE-2018-14349 - NO Response Heap Overflow</p>
<p>CVE-2018-14350 - INTERNALDATE Stack Overflow</p>
<p>CVE-2018-14351 - STATUS Literal Length relative write</p>
<p>CVE-2018-14352 - imap_quote_string off-by-one stack overflow</p>
<p>CVE-2018-14353 - imap_quote_string int underflow</p>
<p>CVE-2018-14354 - imap_subscribe Remote Code Execution</p>
<p>CVE-2018-14355 - STATUS mailbox header cache directory traversal</p>
<p>CVE-2018-14356 - POP empty UID NULL deref</p>
<p>CVE-2018-14357 - LSUB Remote Code Execution</p>
<p>CVE-2018-14358 - RFC822.SIZE Stack Overflow</p>
<p>CVE-2018-14359 - base64 decode Stack Overflow</p>
<p>CVE-2018-14362 - POP Message Cache Directory Traversal</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-14349</cvename>
<cvename>CVE-2018-14350</cvename>
<cvename>CVE-2018-14351</cvename>
<cvename>CVE-2018-14352</cvename>
<cvename>CVE-2018-14353</cvename>
<cvename>CVE-2018-14354</cvename>
<cvename>CVE-2018-14355</cvename>
<cvename>CVE-2018-14356</cvename>
<cvename>CVE-2018-14357</cvename>
<cvename>CVE-2018-14358</cvename>
<cvename>CVE-2018-14359</cvename>
<cvename>CVE-2018-14362</cvename>
<url>http://lists.mutt.org/pipermail/mutt-announce/Week-of-Mon-20180716/000004.html</url>
</references>
<dates>
<discovery>2018-07-15</discovery>
<entry>2018-07-17</entry>
</dates>
</vuln>
<vuln vid="fe12ef83-8b47-11e8-96cc-001a4a7ec6be">
<topic>mutt/neomutt -- multiple vulnerabilities</topic>
<affects>
<package>
<name>neomutt</name>
<range><lt>20180716</lt></range>
</package>
<package>
<name>mutt</name>
<range><lt>1.10.1</lt></range>
</package>
<package>
<name>mutt14</name>
<range><lt>*</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>NeoMutt report:</p>
<blockquote cite="https://github.com/neomutt/neomutt/releases/tag/neomutt-20180716">
<h1>Description</h1>
<h5>CVE-2018-14349</h5><p>NO Response Heap Overflow</p>
<h5>CVE-2018-14350</h5><p>INTERNALDATE Stack Overflow</p>
<h5>CVE-2018-14351</h5><p>STATUS Literal Length relative write</p>
<h5>CVE-2018-14352</h5><p>imap_quote_string off-by-one stack overflow</p>
<h5>CVE-2018-14353</h5><p>imap_quote_string int underflow</p>
<h5>CVE-2018-14354</h5><p>imap_subscribe Remote Code Execution</p>
<h5>CVE-2018-14355</h5><p>STATUS mailbox header cache directory traversal</p>
<h5>CVE-2018-14356</h5><p>POP empty UID NULL deref</p>
<h5>CVE-2018-14357</h5><p>LSUB Remote Code Execution</p>
<h5>CVE-2018-14358</h5><p>RFC822.SIZE Stack Overflow</p>
<h5>CVE-2018-14359</h5><p>base64 decode Stack Overflow</p>
<h5>CVE-2018-14360</h5><p>NNTP Group Stack Overflow</p>
<h5>CVE-2018-14361</h5><p>NNTP Write 1 where via GROUP response</p>
<h5>CVE-2018-14362</h5><p>POP Message Cache Directory Traversal</p>
<h5>CVE-2018-14363</h5><p>NNTP Header Cache Directory Traversal</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-14349</cvename>
<cvename>CVE-2018-14350</cvename>
<cvename>CVE-2018-14351</cvename>
<cvename>CVE-2018-14352</cvename>
<cvename>CVE-2018-14353</cvename>
<cvename>CVE-2018-14354</cvename>
<cvename>CVE-2018-14355</cvename>
<cvename>CVE-2018-14356</cvename>
<cvename>CVE-2018-14357</cvename>
<cvename>CVE-2018-14358</cvename>
<cvename>CVE-2018-14359</cvename>
<cvename>CVE-2018-14360</cvename>
<cvename>CVE-2018-14361</cvename>
<cvename>CVE-2018-14362</cvename>
<cvename>CVE-2018-14363</cvename>
<url>https://github.com/neomutt/neomutt/releases/tag/neomutt-20180716</url>
</references>
<dates>
<discovery>2018-07-10</discovery>
<entry>2018-07-19</entry>
</dates>
</vuln>
<vuln vid="20a1881e-8a9e-11e8-bddf-d017c2ca229d">
<topic>jenkins -- multiple vulnerabilities</topic>
<affects>
<package>
<name>jenkins</name>
<range><lt>2.133</lt></range>
</package>
<package>
<name>jenkins-lts</name>
<range><lt>2.121.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Jenkins Security Advisory:</p>
<blockquote cite="https://jenkins.io/security/advisory/2018-07-18/">
<h1>Description</h1>
<h5>(High) SECURITY-897 / CVE-2018-1999001</h5>
<p>Users without Overall/Read permission can have Jenkins reset parts of global configuration on the next restart </p>
<h5>(High) SECURITY-914 / CVE-2018-1999002</h5>
<p>Arbitrary file read vulnerability</p>
<h5>(Medium) SECURITY-891 / CVE-2018-1999003</h5>
<p>Unauthorized users could cancel queued builds</p>
<h5>(Medium) SECURITY-892 / CVE-2018-1999004</h5>
<p>Unauthorized users could initiate and abort agent launches</p>
<h5>(Medium) SECURITY-944 / CVE-2018-1999005</h5>
<p>Stored XSS vulnerability</p>
<h5>(Medium) SECURITY-925 / CVE-2018-1999006</h5>
<p>Unauthorized users are able to determine when a plugin was extracted from its JPI package</p>
<h5>(Medium) SECURITY-390 / CVE-2018-1999007</h5>
<p>XSS vulnerability in Stapler debug mode</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-1999001</cvename>
<cvename>CVE-2018-1999002</cvename>
<cvename>CVE-2018-1999003</cvename>
<cvename>CVE-2018-1999004</cvename>
<cvename>CVE-2018-1999005</cvename>
<cvename>CVE-2018-1999006</cvename>
<cvename>CVE-2018-1999007</cvename>
<url>https://jenkins.io/security/advisory/2018-07-18/</url>
</references>
<dates>
<discovery>2018-07-18</discovery>
<entry>2018-07-18</entry>
</dates>
</vuln>
<vuln vid="c6d1a8a6-8a91-11e8-be4d-005056925db4">
<topic>znc -- multiple vulnerabilities</topic>
<affects>
<package>
<name>znc</name>
<range><lt>1.7.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mitre reports:</p>
<blockquote cite="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14055">
<p>ZNC before 1.7.1-rc1 does not properly validate untrusted lines
coming from the network, allowing a non-admin user to escalate his
privilege and inject rogue values into znc.conf.</p>
</blockquote>
<blockquote cite="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14056">
<p>ZNC before 1.7.1-rc1 is prone to a path traversal flaw via ../ in
a web skin name to access files outside of the intended skins
directories.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-14055</cvename>
<cvename>CVE-2018-14056</cvename>
<url>https://wiki.znc.in/ChangeLog/1.7.1</url>
</references>
<dates>
<discovery>2018-07-14</discovery>
<entry>2018-07-18</entry>
</dates>
</vuln>
<vuln vid="8b1a50ab-8a8e-11e8-add2-b499baebfeaf">
<topic>Apache httpd -- multiple vulnerabilities</topic>
<affects>
<package>
<name>apache24</name>
<range><lt>2.4.34</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Apache project reports:</p>
<blockquote cite="http://httpd.apache.org/security/vulnerabilities_24.html">
<ul>
<li>DoS for HTTP/2 connections by crafted requests
(CVE-2018-1333). By specially crafting HTTP/2 requests, workers
would be allocated 60 seconds longer than necessary, leading to
worker exhaustion and a denial of service. (low)</li>
<li>mod_md, DoS via Coredumps on specially crafted requests
(CVE-2018-8011). By specially crafting HTTP requests, the mod_md
challenge handler would dereference a NULL pointer and cause the
child process to segfault. This could be used to DoS the server.
(moderate)</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>http://httpd.apache.org/security/vulnerabilities_24.html</url>
<cvename>CVE-2018-1333</cvename>
<cvename>CVE-2018-8011</cvename>
</references>
<dates>
<discovery>2018-07-18</discovery>
<entry>2018-07-18</entry>
</dates>
</vuln>
<vuln vid="8fc615cc-8a66-11e8-8c75-d8cb8abf62dd">
<topic>Gitlab -- Remote Code Execution Vulnerability in GitLab Projects Import</topic>
<affects>
<package>
<name>gitlab-ce</name>
<name>gitlab</name>
<range><ge>11.0.0</ge><lt>11.0.4</lt></range>
<range><ge>10.8.0</ge><lt>10.8.6</lt></range>
<range><ge>8.9.0</ge><lt>10.7.7</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/07/17/critical-security-release-gitlab-11-dot-0-dot-4-released/">
<p>Remote Code Execution Vulnerability in GitLab Projects Import</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-14364</cvename>
<url>https://about.gitlab.com/2018/07/17/critical-security-release-gitlab-11-dot-0-dot-4-released/</url>
</references>
<dates>
<discovery>2018-07-17</discovery>
<entry>2018-07-18</entry>
</dates>
</vuln>
<vuln vid="ef013039-89cd-11e8-84e9-00e04c1ea73d">
<topic>typo3 -- multiple vulnerabilities</topic>
<affects>
<package>
<name>typo3-7</name>
<range><lt>7.6.30</lt></range>
</package>
<package>
<name>typo3-8</name>
<range><lt>8.7.17</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Typo3 core team reports:</p>
<blockquote cite="https://typo3.org/article/typo3-931-8717-and-7630-security-releases-published/">
<p>It has been discovered that TYPO3’s Salted Password system extension (which is a mandatory system component)
is vulnerable to Authentication Bypass when using hashing methods which are related by PHP class inheritance.
In standard TYPO3 core distributions stored passwords using the blowfish hashing algorithm can be overridden
when using MD5 as the default hashing algorithm by just knowing a valid username.
Per default the Portable PHP hashing algorithm (PHPass) is used which is not vulnerable.</p>
<p>Phar files (formerly known as "PHP archives") can act als self extracting archives which leads to the fact
that source code is executed when Phar files are invoked. The Phar file format is not limited to be stored
with a dedicated file extension - "bundle.phar" would be valid as well as "bundle.txt" would be. This way,
Phar files can be obfuscated as image or text file which would not be denied from being uploaded and persisted
to a TYPO3 installation. Due to a missing sanitization of user input, those Phar files can be invoked by
manipulated URLs in TYPO3 backend forms. A valid backend user account is needed to exploit this vulnerability.
In theory the attack vector would be possible in the TYPO3 frontend as well, however no functional exploit
has been identified so far.</p>
<p>Failing to properly dissociate system related configuration from user generated configuration,
the Form Framework (system extension "form") is vulnerable to SQL injection and Privilege Escalation.
Basically instructions can be persisted to a form definition file that were not configured to be modified -
this applies to definitions managed using the form editor module as well as direct file upload using the regular
file list module. A valid backend user account as well as having system extension form activated are needed
in order to exploit this vulnerability.</p>
<p>It has been discovered that the Form Framework (system extension "form") is vulnerable to Insecure Deserialization
when being used with the additional PHP PECL package “yaml”, which is capable of unserializing YAML contents
to PHP objects. A valid backend user account as well as having PHP setting "yaml.decode_php" enabled is needed
to exploit this vulnerability.</p>
</blockquote>
</body>
</description>
<references>
<url>https://typo3.org/security/advisory/typo3-core-sa-2018-001/</url>
<url>https://typo3.org/security/advisory/typo3-core-sa-2018-002/</url>
<url>https://typo3.org/security/advisory/typo3-core-sa-2018-003/</url>
<url>https://typo3.org/security/advisory/typo3-core-sa-2018-004/</url>
</references>
<dates>
<discovery>2018-07-12</discovery>
<entry>2018-07-17</entry>
</dates>
</vuln>
<vuln vid="fe93803c-883f-11e8-9f0c-001b216d295b">
<topic>Several Security Defects in the Bouncy Castle Crypto APIs</topic>
<affects>
<package>
<name>bouncycastle15</name>
<range><lt>1.60</lt></range>
</package>
<package>
<name>puppetserver</name>
<range><ge>0</ge></range>
</package>
<package>
<name>puppetserver5</name>
<range><lt>5.3.8</lt></range>
</package>
<package>
<name>puppetserver6</name>
<range><lt>6.2.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Legion of the Bouncy Castle reports:</p>
<blockquote cite="https://www.bouncycastle.org/latest_releases.html">
<p>Release 1.60 is now available for download.</p>
<p>CVE-2018-1000180: issue around primality tests for RSA key pair
generation if done using only the low-level API.</p>
<p>CVE-2018-1000613: lack of class checking in deserialization
of XMSS/XMSS^MT private keys with BDS state information.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-1000180</cvename>
<cvename>CVE-2018-1000613</cvename>
<url>https://www.bouncycastle.org/latest_releases.html</url>
</references>
<dates>
<discovery>2018-06-30</discovery>
<entry>2018-07-15</entry>
</dates>
</vuln>
<vuln vid="bd6cf187-8710-11e8-833d-18a6f7016652">
<topic>qutebrowser -- Remote code execution due to CSRF</topic>
<affects>
<package>
<name>qutebrowser</name>
<range><ge>1.4.0</ge><lt>1.4.1</lt></range>
<range><ge>1.0.0</ge><lt>1.3.3_1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>qutebrowser team reports:</p>
<blockquote cite="https://blog.qutebrowser.org/cve-2018-10895-remote-code-execution-due-to-csrf-in-qutebrowser.html">
<p>Due to a CSRF vulnerability affecting the qute://settings page,
it was possible for websites to modify qutebrowser settings.
Via settings like editor.command, this possibly allowed websites
to execute arbitrary code.</p>
</blockquote>
</body>
</description>
<references>
<url>http://seclists.org/oss-sec/2018/q3/29</url>
<cvename>CVE-2018-10895</cvename>
</references>
<dates>
<discovery>2018-07-11</discovery>
<entry>2018-07-14</entry>
</dates>
</vuln>
<vuln vid="e78732b2-8528-11e8-9c42-6451062f0f7a">
<topic>Flash Player -- multiple vulnerabilities</topic>
<affects>
<package>
<name>linux-flashplayer</name>
<range><lt>30.0.0.134</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Adobe reports:</p>
<blockquote cite="https://helpx.adobe.com/security/products/flash-player/apsb18-24.html">
<ul>
<li>This update resolves an out-of-bounds read vulnerability that
could lead to information disclosure (CVE-2018-5008).</li>
<li>This update resolves a type confusion vulnerability that
could lead to arbitrary code execution (CVE-2018-5007).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-5007</cvename>
<cvename>CVE-2018-5008</cvename>
<url>https://helpx.adobe.com/security/products/flash-player/apsb18-24.html</url>
</references>
<dates>
<discovery>2018-07-10</discovery>
<entry>2018-07-11</entry>
</dates>
</vuln>
<vuln vid="1e54d140-8493-11e8-a795-0028f8d09152">
<topic>couchdb -- multiple vulnerabilities</topic>
<affects>
<package>
<name>couchdb</name>
<range><lt>1.7.2,2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Apache CouchDB PMC reports:</p>
<blockquote cite="https://blog.couchdb.org/2018/07/10/cve-2018-8007/">
<p>Database Administrator could achieve privilege escalation to
the account that CouchDB runs under, by abusing insufficient validation
in the HTTP API, escaping security controls implemented in previous
releases.</p>
</blockquote>
</body>
</description>
<references>
<url>https://blog.couchdb.org/2018/07/10/cve-2018-8007/</url>
<cvename>CVE-2018-8007</cvename>
<url>https://blog.couchdb.org/2017/11/14/apache-couchdb-cve-2017-12635-and-cve-2017-12636/</url>
<cvename>CVE-2017-12636</cvename>
<cvename>CVE-2017-12635</cvename>
<url>https://lists.apache.org/thread.html/6fa798e96686b7b0013ec2088140d00aeb7d34487d3f5ad032af6934@%3Cdev.couchdb.apache.org%3E</url>
</references>
<dates>
<discovery>2017-11-14</discovery>
<entry>2018-07-10</entry>
</dates>
</vuln>
<vuln vid="3c9b7698-84da-11e8-8c75-d8cb8abf62dd">
<topic>Libgit2 -- multiple vulnerabilities</topic>
<affects>
<package>
<name>libgit2</name>
<range><lt>0.27.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Git community reports:</p>
<blockquote cite="https://github.com/libgit2/libgit2/releases/tag/v0.27.3">
<p>Out-of-bounds reads when reading objects from a packfile</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/libgit2/libgit2/releases/tag/v0.27.3</url>
<cvename>CVE-2018-10887</cvename>
<cvename>CVE-2018-10888</cvename>
</references>
<dates>
<discovery>2018-07-09</discovery>
<entry>2018-07-11</entry>
</dates>
</vuln>
<vuln vid="d1e9d8c5-839b-11e8-9610-9c5c8e75236a">
<topic>clamav -- multiple vulnerabilities</topic>
<affects>
<package>
<name>clamav</name>
<range><lt>0.100.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p> Joel Esler reports:</p>
<blockquote cite="https://blog.clamav.net/2018/07/clamav-01001-has-been-released.html">
<p>3 security fixes in this release:</p>
<ul>
<li>CVE-2017-16932: Vulnerability in libxml2 dependency (affects ClamAV on Windows only).</li>
<li>CVE-2018-0360: HWP integer overflow, infinite loop vulnerability. Reported by Secunia Research at Flexera.</li>
<li>CVE-2018-0361: ClamAV PDF object length check, unreasonably long time to parse relatively small file. Report
ed by aCaB.</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://blog.clamav.net/2018/07/clamav-01001-has-been-released.html</url>
<cvename>CVE-2017-16932</cvename>
<cvename>CVE-2018-0360</cvename>
<cvename>CVE-2018-0361</cvename>
</references>
<dates>
<discovery>2018-07-09</discovery>
<entry>2018-07-09</entry>
</dates>
</vuln>
<vuln vid="7764b219-8148-11e8-aa4d-000e0cd7b374">
<topic>zziplib - multiple vulnerabilities</topic>
<affects>
<package>
<name>zziplib</name>
<range><lt>0.13.68</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>NIST reports (by search in the range 2017/01/01 - 2018/07/06):</p>
<blockquote cite="https://nvd.nist.gov/vuln/search/results?form_type=Advanced&results_type=overview&query=zziplib&search_type=all&pub_start_date=01%2F01%2F2017&pub_end_date=07%2F06%2F2018">
<p>17 security fixes in this release:</p>
<ul>
<li>Heap-based buffer overflow in the __zzip_get32 function in fetch.c.</li>
<li>Heap-based buffer overflow in the __zzip_get64 function in fetch.c.</li>
<li>Heap-based buffer overflow in the zzip_mem_entry_extra_block function
in memdisk.c.</li>
<li>The zzip_mem_entry_new function in memdisk.c allows remote attackers
to cause a denial of service (out-of-bounds read and crash) via a
crafted ZIP file.</li>
<li>The prescan_entry function in fseeko.c allows remote attackers to cause
a denial of service (NULL pointer dereference and crash) via crafted
ZIP file.</li>
<li>The zzip_mem_entry_new function in memdisk.c cause a NULL pointer
dereference and crash via a crafted ZIP file.</li>
<li>seeko.c cause a denial of service (assertion failure and crash) via a
crafted ZIP file.</li>
<li>A segmentation fault caused by invalid memory access in the
zzip_disk_fread function because the size variable is not validated
against the amount of file->stored data.</li>
<li>A memory alignment error and bus error in the __zzip_fetch_disk_trailer
function of zzip/zip.c.</li>
<li>A bus error caused by loading of a misaligned address in the
zzip_disk_findfirst function.</li>
<li>An uncontrolled memory allocation and a crash in the __zzip_parse_root_directory
function.</li>
<li>An invalid memory address dereference was discovered in zzip_disk_fread
in mmapped.c.</li>
<li>A memory leak triggered in the function zzip_mem_disk_new in
memdisk.c.</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-5974</cvename>
<cvename>CVE-2017-5975</cvename>
<cvename>CVE-2017-5976</cvename>
<cvename>CVE-2017-5977</cvename>
<cvename>CVE-2017-5978</cvename>
<cvename>CVE-2017-5979</cvename>
<cvename>CVE-2017-5980</cvename>
<cvename>CVE-2017-5981</cvename>
<cvename>CVE-2018-6381</cvename>
<cvename>CVE-2018-6484</cvename>
<cvename>CVE-2018-6540</cvename>
<cvename>CVE-2018-6541</cvename>
<cvename>CVE-2018-6542</cvename>
<cvename>CVE-2018-6869</cvename>
<cvename>CVE-2018-7725</cvename>
<cvename>CVE-2018-7726</cvename>
<cvename>CVE-2018-7727</cvename>
<url>https://nvd.nist.gov/vuln/search/results?form_type=Advanced&results_type=overview&query=zziplib&search_type=all&pub_start_date=01%2F01%2F2017&pub_end_date=07%2F06%2F2018"</url>
</references>
<dates>
<discovery>2017-03-01</discovery>
<entry>2018-07-06</entry>
</dates>
</vuln>
<vuln vid="4740174c-82bb-11e8-a29a-00e04c1ea73d">
<topic>wordpress -- multiple issues</topic>
<affects>
<package>
<name>wordpress</name>
<name>fr-wordpress</name>
<range><lt>4.9.7,1</lt></range>
</package>
<package>
<name>de-wordpress</name>
<name>zh_CN-wordpress</name>
<name>zh_TW-wordpress</name>
<name>ja-wordpress</name>
<name>ru-wordpress</name>
<range><lt>4.9.7</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>wordpressdevelopers reports:</p>
<blockquote cite="https://wordpress.org/news/2018/07/wordpress-4-9-7-security-and-maintenance-release/">
<p>Taxonomy: Improve cache handling for term queries.</p>
<p>Posts, Post Types: Clear post password cookie when logging out.</p>
<p>Widgets: Allow basic HTML tags in sidebar descriptions on Widgets admin screen.</p>
<p>Community Events Dashboard: Always show the nearest WordCamp if one is coming up, even if there are multiple Meetups happening first.</p>
<p>Privacy: Make sure default privacy policy content does not cause a fatal error when flushing rewrite rules outside of the admin context.</p>
</blockquote>
</body>
</description>
<references>
<url>https://wordpress.org/news/2018/07/wordpress-4-9-7-security-and-maintenance-release/</url>
</references>
<dates>
<discovery>2018-07-05</discovery>
<entry>2018-07-08</entry>
</dates>
</vuln>
<vuln vid="bfd5d004-81d4-11e8-a29a-00e04c1ea73d">
<topic>mybb -- vulnerabilities</topic>
<affects>
<package>
<name>mybb</name>
<range><lt>1.8.16</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>mybb Team reports:</p>
<blockquote cite="https://blog.mybb.com/2018/07/04/mybb-1-8-16-released-security-maintenance-release/">
<p>High risk: Image and URL MyCode Persistent XSS</p>
<p>Medium risk: Multipage Reflected XSS</p>
<p>Low risk: ACP logs XSS</p>
<p>Low risk: Arbitrary file deletion via ACP’s Settings</p>
<p>Low risk: Login CSRF</p>
<p>Low risk: Non-video content embedding via Video MyCode</p>
</blockquote>
</body>
</description>
<references>
<url>https://blog.mybb.com/2018/07/04/mybb-1-8-16-released-security-maintenance-release/</url>
</references>
<dates>
<discovery>2018-07-04</discovery>
<entry>2018-07-07</entry>
</dates>
</vuln>
<vuln vid="e375ff3f-7fec-11e8-8088-28d244aee256">
<topic>expat -- multiple vulnerabilities</topic>
<affects>
<package>
<name>expat</name>
<range><lt>2.2.1</lt></range>
</package>
<package>
<name>libwww</name>
<range><lt>5.4.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mitre reports:</p>
<blockquote cite="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9063">
<p>An integer overflow during the parsing of XML using the Expat library.</p>
</blockquote>
<blockquote cite="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9233">
<p>XML External Entity vulnerability in libexpat 2.2.0 and earlier (Expat
XML Parser Library) allows attackers to put the parser in an infinite
loop using a malformed external entity definition from an external DTD.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2016-9063</cvename>
<cvename>CVE-2017-9233</cvename>
<url>http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9063</url>
<url>http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9233</url>
<url>https://libexpat.github.io/doc/cve-2017-9233/</url>
</references>
<dates>
<discovery>2016-10-27</discovery>
<entry>2018-07-05</entry>
</dates>
</vuln>
<vuln vid="ce39379f-7eb7-11e8-ab03-00bd7f19ff09">
<topic>h2o -- heap buffer overflow during logging</topic>
<affects>
<package>
<name>h2o</name>
<range><lt>2.2.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Marlies Ruck reports:</p>
<blockquote cite="https://github.com/h2o/h2o/releases/tag/v2.2.5">
<p>Fix heap buffer overflow while trying to emit access log
- see references for full details.</p>
<p>CVE-2018-0608: Buffer overflow in H2O version 2.2.4 and
earlier allows remote attackers to execute arbitrary code or
cause a denial of service (DoS) via unspecified vectors.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-0608</cvename>
<url>https://github.com/h2o/h2o/issues/1775</url>
<url>https://github.com/h2o/h2o/releases/tag/v2.2.5</url>
</references>
<dates>
<discovery>2018-06-01</discovery>
<entry>2018-07-03</entry>
</dates>
</vuln>
<vuln vid="c1630aa3-7970-11e8-8634-dcfe074bd614">
<topic>SQLite -- Corrupt DB can cause a NULL pointer dereference</topic>
<affects>
<package>
<name>upp</name>
<range><le>11540</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>MITRE reports:</p>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2018-8740">
<p>SQLite databases whose schema is corrupted using a CREATE TABLE AS
statement could cause a NULL pointer dereference, related to build.c
and prepare.c.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-8740</cvename>
<url>http://openwall.com/lists/oss-security/2018/03/17/1</url>
</references>
<dates>
<discovery>2018-03-16</discovery>
<entry>2018-07-01</entry>
</dates>
</vuln>
<vuln vid="cd81806c-26e7-4d4a-8425-02724a2f48af">
<topic>mozilla -- multiple vulnerabilities</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>61.0_1,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.2.1.19_2</lt></range>
</package>
<package>
<name>seamonkey</name>
<name>linux-seamonkey</name>
<range><lt>2.49.4</lt></range>
</package>
<package>
<name>firefox-esr</name>
<range><ge>60.0,1</ge><lt>60.1.0_1,1</lt></range>
<range><lt>52.9.0_1,1</lt></range>
</package>
<package>
<name>linux-firefox</name>
<range><lt>52.9.0,2</lt></range>
</package>
<package>
<name>libxul</name>
<name>thunderbird</name>
<name>linux-thunderbird</name>
<range><lt>52.9.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-15/">
<p>CVE-2018-12359: Buffer overflow using computed size of canvas element</p>
<p>CVE-2018-12360: Use-after-free when using focus()</p>
<p>CVE-2018-12361: Integer overflow in SwizzleData</p>
<p>CVE-2018-12358: Same-origin bypass using service worker and redirection</p>
<p>CVE-2018-12362: Integer overflow in SSSE3 scaler</p>
<p>CVE-2018-5156: Media recorder segmentation fault when track type is changed during capture</p>
<p>CVE-2018-12363: Use-after-free when appending DOM nodes</p>
<p>CVE-2018-12364: CSRF attacks through 307 redirects and NPAPI plugins</p>
<p>CVE-2018-12365: Compromised IPC child process can list local filenames</p>
<p>CVE-2018-12371: Integer overflow in Skia library during edge builder allocation</p>
<p>CVE-2018-12366: Invalid data handling during QCMS transformations</p>
<p>CVE-2018-12367: Timing attack mitigation of PerformanceNavigationTiming</p>
<p>CVE-2018-12368: No warning when opening executable SettingContent-ms files</p>
<p>CVE-2018-12369: WebExtension security permission checks bypassed by embedded experiments</p>
<p>CVE-2018-12370: SameSite cookie protections bypassed when exiting Reader View</p>
<p>CVE-2018-5186: Memory safety bugs fixed in Firefox 61</p>
<p>CVE-2018-5187: Memory safety bugs fixed in Firefox 60 and Firefox ESR 60.1</p>
<p>CVE-2018-5188: Memory safety bugs fixed in Firefox 60, Firefox ESR 60.1, and Firefox ESR 52.9</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-5156</cvename>
<cvename>CVE-2018-5186</cvename>
<cvename>CVE-2018-5187</cvename>
<cvename>CVE-2018-5188</cvename>
<cvename>CVE-2018-12358</cvename>
<cvename>CVE-2018-12359</cvename>
<cvename>CVE-2018-12360</cvename>
<cvename>CVE-2018-12361</cvename>
<cvename>CVE-2018-12362</cvename>
<cvename>CVE-2018-12363</cvename>
<cvename>CVE-2018-12364</cvename>
<cvename>CVE-2018-12365</cvename>
<cvename>CVE-2018-12366</cvename>
<cvename>CVE-2018-12367</cvename>
<cvename>CVE-2018-12368</cvename>
<cvename>CVE-2018-12369</cvename>
<cvename>CVE-2018-12370</cvename>
<cvename>CVE-2018-12371</cvename>
<url>https://www.mozilla.org/en-US/security/advisories/mfsa2018-15/</url>
<url>https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/</url>
<url>https://www.mozilla.org/en-US/security/advisories/mfsa2018-17/</url>
</references>
<dates>
<discovery>2018-06-26</discovery>
<entry>2018-06-26</entry>
<modified>2018-07-07</modified>
</dates>
</vuln>
<vuln vid="739948e3-78bf-11e8-b23c-080027ac955c">
<topic>mailman -- hardening against malicious listowners injecting evil HTML scripts</topic>
<affects>
<package> <name>mailman</name> <range><lt>2.1.27</lt></range> </package>
<package> <name>mailman-with-htdig</name> <range><lt>2.1.27</lt></range> </package>
<package> <name>ja-mailman</name> <range><lt>2.1.14.j7_5,1</lt></range> </package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mark Sapiro reports:</p>
<blockquote cite="https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/NEWS#L8">
<p>Existing protections against malicious listowners injecting evil
scripts into listinfo pages have had a few more checks added.
</p>
<p>A few more error messages have had their values HTML escaped.</p>
<p>The hash generated when SUBSCRIBE_FORM_SECRET is set could have been
the same as one generated at the same time for a different list and
IP address.</p>
</blockquote>
</body>
</description>
<references>
<url>https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/NEWS#L8</url>
<url>https://www.mail-archive.com/mailman-users@python.org/</url>
<cvename>CVE-2018-0618</cvename>
</references>
<dates>
<discovery>2018-03-09</discovery> <!-- Launchpad rev. 1747 -->
<entry>2018-06-25</entry>
</dates>
</vuln>
<vuln vid="b950a83b-789e-11e8-8545-d8cb8abf62dd">
<topic>Gitlab -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab</name>
<range><ge>11.0.0</ge><lt>11.0.1</lt></range>
<range><ge>10.8.0</ge><lt>10.8.5</lt></range>
<range><ge>4.1</ge><lt>10.7.6</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/06/25/security-release-gitlab-11-dot-0-dot-1-released/">
<p>Wiki XSS</p>
<p>Sanitize gem updates</p>
<p>XSS in url_for(params)</p>
<p>Content injection via username</p>
<p>Activity feed publicly displaying internal project names</p>
<p>Persistent XSS in charts</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-12606</cvename>
<cvename>CVE-2018-3740</cvename>
<cvename>CVE-2018-12605</cvename>
<cvename>CVE-2018-12607</cvename>
<url>https://about.gitlab.com/2018/06/25/security-release-gitlab-11-dot-0-dot-1-released/</url>
</references>
<dates>
<discovery>2018-06-25</discovery>
<entry>2018-06-25</entry>
</dates>
</vuln>
<vuln vid="17cb6ff3-7670-11e8-8854-6805ca0b3d42">
<topic>phpmyadmin -- remote code inclusion and XSS scripting</topic>
<affects>
<package>
<name>phpmyadmin</name>
<range><lt>4.8.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The phpMyAdmin development team reports:</p>
<blockquote cite="https://www.phpmyadmin.net/security/PMASA-2018-3/">
<h3>Summary</h3>
<p>XSS in Designer feature</p>
<h3>Description</h3>
<p>A Cross-Site Scripting vulnerability was found in the
Designer feature, where an attacker can deliver a
payload to a user through a specially-crafted database
name.</p>
<h3>Severity</h3>
<p>We consider this attack to be of moderate severity.</p>
</blockquote>
<blockquote cite="https://www.phpmyadmin.net/security/PMASA-2018-4/">
<h3>Summary</h3>
<p>File inclusion and remote code execution attack</p>
<h3>Description</h3>
<p>A flaw has been discovered where an attacker can include
(view and potentially execute) files on the server.</p>
<p>The vulnerability comes from a portion of code where
pages are redirected and loaded within phpMyAdmin, and an
improper test for whitelisted pages.</p>
<p>An attacker must be authenticated, except in these
situations:</p>
<ul>
<li>$cfg['AllowArbitraryServer'] = true: attacker can
specify any host he/she is already in control of, and
execute arbitrary code on phpMyAdmin</li>
<li>$cfg['ServerDefault'] = 0: this bypasses the login and
runs the vulnerable code without any authentication</li>
</ul>
<h3>Severity</h3>
<p>We consider this to be severe.</p> <h3>Mitigation
factor</h3> <p>Configuring PHP with a restrictive
`open_basedir` can greatly restrict an attacker's ability to
view files on the server. Vulnerable systems should not be
run with the phpMyAdmin directives
$cfg['AllowArbitraryServer'] = true or $cfg['ServerDefault']
= 0</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.phpmyadmin.net/security/PMASA-2018-3/</url>
<url>https://www.phpmyadmin.net/security/PMASA-2018-4/</url>
<cvename>CVE-2018-12581</cvename>
<cvename>CVE-2018-12613</cvename>
</references>
<dates>
<discovery>2018-06-21</discovery>
<entry>2018-06-22</entry>
</dates>
</vuln>
<vuln vid="4e07d94f-75a5-11e8-85d1-a4badb2f4699">
<topic>FreeBSD -- Lazy FPU State Restore Information Disclosure</topic>
<affects>
<package>
<name>FreeBSD-kernel</name>
<range><ge>11.1</ge><lt>11.1_11</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>A subset of Intel processors can allow a local thread
to infer data from another thread through a speculative
execution side channel when Lazy FPU state restore is
used.</p>
<h1>Impact:</h1>
<p>Any local thread can potentially read FPU state information
from other threads running on the host. This could include
cryptographic keys when the AES-NI CPU feature is present.</p>
</body>
</description>
<references>
<cvename>CVE-2018-3665</cvename>
<freebsdsa>SA-18:07.lazyfpu</freebsdsa>
</references>
<dates>
<discovery>2018-06-21</discovery>
<entry>2018-06-21</entry>
</dates>
</vuln>
<vuln vid="25f73c47-68a8-4a30-9cbc-1ca5eea4d6ba">
<topic>GraphicsMagick -- multiple vulnerabilities</topic>
<affects>
<package>
<name>GraphicsMagick</name>
<range><lt>1.3.26,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GraphicsMagick reports:</p>
<blockquote cite="http://www.graphicsmagick.org/NEWS.html">
<p>Multiple vulnerabilities have been found in GraphicsMagick 1.3.26
or earlier. Please refer to the CVE list for details.</p>
</blockquote>
</body>
</description>
<references>
<url>http://www.graphicsmagick.org/NEWS.html</url>
<cvename>CVE-2016-7800</cvename>
<cvename>CVE-2016-7996</cvename>
<cvename>CVE-2016-7997</cvename>
<cvename>CVE-2016-9830</cvename>
<cvename>CVE-2017-6335</cvename>
<cvename>CVE-2017-8350</cvename>
<cvename>CVE-2017-10794</cvename>
<cvename>CVE-2017-10799</cvename>
<cvename>CVE-2017-10800</cvename>
</references>
<dates>
<discovery>2017-07-04</discovery>
<entry>2018-06-18</entry>
</dates>
</vuln>
<vuln vid="3a66cb69-716f-11e8-be54-3085a9a47796">
<topic>slurm -- insecure handling of user_name and gid fields</topic>
<affects>
<package>
<name>slurm-wlm</name>
<range><lt>17.02.11</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>SchedMD reports:</p>
<blockquote cite="https://lists.schedmd.com/pipermail/slurm-announce/2018/000008.html">
<h1>Insecure handling of user_name and gid fields (CVE-2018-10995)</h1>
<p>While fixes are only available for the supported 17.02 and 17.11
releases, it is believed that similar vulnerabilities do affect past
versions as well. The only resolution is to upgrade Slurm to a fixed
release.</p>
</blockquote>
</body>
</description>
<references>
<url>https://lists.schedmd.com/pipermail/slurm-announce/2018/000008.html</url>
</references>
<dates>
<discovery>2018-05-30</discovery>
<entry>2018-06-16</entry>
</dates>
</vuln>
<vuln vid="45b8e2eb-7056-11e8-8fab-63ca6e0e13a2">
<topic>node.js -- multiple vulnerabilities</topic>
<affects>
<package>
<name>node6</name>
<range><lt>6.14.3</lt></range>
</package>
<package>
<name>node8</name>
<range><lt>8.11.3</lt></range>
</package>
<package>
<name>node</name>
<range><lt>10.4.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Node.js reports:</p>
<blockquote cite="https://nodejs.org/en/blog/vulnerability/june-2018-security-releases/">
<h1>Denial of Service Vulnerability in HTTP/2 (CVE-2018-7161)</h1>
<p>All versions of 8.x and later are vulnerable and the severity is
HIGH. An attacker can cause a denial of service (DoS) by causing a
node server providing an http2 server to crash. This can be
accomplished by interacting with the http2 server in a manner that
triggers a cleanup bug where objects are used in native code after
they are no longer available. This has been addressed by updating
the http2 implementation. Thanks to Jordan Zebor at F5 Networks for
reporting this issue.</p>
<h1>Denial of Service, nghttp2 dependency (CVE-2018-1000168)</h1>
<p>All versions of 9.x and later are vulnerable and the severity is
HIGH. Under certain conditions, a malicious client can trigger an
uninitialized read (and a subsequent segfault) by sending a
malformed ALTSVC frame. This has been addressed through an by
updating nghttp2.</p>
<h1>Denial of Service Vulnerability in TLS (CVE-2018-7162)</h1>
<p>All versions of 9.x and later are vulnerable and the severity is
HIGH. An attacker can cause a denial of service (DoS) by causing a
node process which provides an http server supporting TLS server to
crash. This can be accomplished by sending duplicate/unexpected
messages during the handshake. This vulnerability has been addressed
by updating the TLS implementation. Thanks to Jordan Zebor at F5
Networks all of his help investigating this issue with the Node.js
team.</p>
<h1>Memory exhaustion DoS on v9.x (CVE-2018-7164)</h1>
<p>Versions 9.7.0 and later are vulnerable and the severity is MEDIUM.
A bug introduced in 9.7.0 increases the memory consumed when reading
from the network into JavaScript using the net.Socket object
directly as a stream. An attacker could use this cause a denial of
service by sending tiny chunks of data in short succession. This
vulnerability was restored by reverting to the prior behaviour.</p>
<h1>Calls to Buffer.fill() and/or Buffer.alloc() may hang (CVE-2018-7167)</h1>
<p>Calling Buffer.fill() or Buffer.alloc() with some parameters can
lead to a hang which could result in a Denial of Service. In order
to address this vulnerability, the implementations of Buffer.alloc()
and Buffer.fill() were updated so that they zero fill instead of
hanging in these cases.</p>
</blockquote>
</body>
</description>
<references>
<url>https://nodejs.org/en/blog/vulnerability/june-2018-security-releases/</url>
<url>https://nghttp2.org/blog/2018/04/12/nghttp2-v1-31-1/</url>
<cvename>CVE-2018-7161</cvename>
<cvename>CVE-2018-7162</cvename>
<cvename>CVE-2018-7164</cvename>
<cvename>CVE-2018-7167</cvename>
<cvename>CVE-2018-1000168</cvename>
</references>
<dates>
<discovery>2018-06-12</discovery>
<entry>2018-06-15</entry>
</dates>
</vuln>
<vuln vid="53eb9e1e-7014-11e8-8b1f-3065ec8fd3ec">
<topic>password-store -- GPG parsing vulnerabilities</topic>
<affects>
<package>
<name>password-store</name>
<range><lt>1.7.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Jason A. Donenfeld reports:</p>
<blockquote cite="https://lists.zx2c4.com/pipermail/password-store/2018-June/003308.html">
<p>Markus Brinkmann discovered that [the] parsing of gpg command line
output with regexes isn't anchored to the beginning of the line,
which means an attacker can generate a malicious key that simply has
the verification string as part of its username.</p>
<p>This has a number of nasty consequences:</p>
<ul>
<li>an attacker who manages to write into your ~/.password-store
and also inject a malicious key into your keyring can replace
your .gpg-id key and have your passwords encrypted under
additional keys;</li>
<li>if you have extensions enabled (disabled by default), an
attacker who manages to write into your ~/.password-store and
also inject a malicious key into your keyring can replace your
extensions and hence execute code.</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://lists.zx2c4.com/pipermail/password-store/2018-June/003308.html</url>
<cvename>CVE-2018-12356</cvename>
</references>
<dates>
<discovery>2018-06-14</discovery>
<entry>2018-06-14</entry>
</dates>
</vuln>
<vuln vid="9b5162de-6f39-11e8-818e-e8e0b747a45a">
<topic>libgcrypt -- side-channel attack vulnerability</topic>
<affects>
<package>
<name>libgcrypt</name>
<range><lt>1.8.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GnuPG reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0495">
<p>Mitigate a local side-channel attack on ECDSA signature as described in the white paper "Return on the Hidden Number Problem".</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-0495</cvename>
<url>https://www.nccgroup.trust/us/our-research/technical-advisory-return-of-the-hidden-number-problem/</url>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0495</url>
<url>https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.7.4-relnotes.txt</url>
</references>
<dates>
<discovery>2018-06-13</discovery>
<entry>2018-06-13</entry>
<modified>2018-06-14</modified>
</dates>
</vuln>
<vuln vid="c82ecac5-6e3f-11e8-8777-b499baebfeaf">
<topic>OpenSSL -- Client DoS due to large DH parameter</topic>
<affects>
<package>
<name>libressl</name>
<name>libressl-devel</name>
<range><lt>2.6.5</lt></range>
<range><ge>2.7.0</ge><lt>2.7.4</lt></range>
</package>
<package>
<name>openssl</name>
<range><lt>1.0.2o_4,1</lt></range>
</package>
<package>
<name>openssl-devel</name>
<range><lt>1.1.0h_2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The OpenSSL project reports:</p>
<blockquote cite="https://www.openssl.org/news/secadv/20180612.txt">
<p>During key agreement in a TLS handshake using a DH(E) based
ciphersuite a malicious server can send a very large prime value
to the client. This will cause the client to spend an unreasonably
long period of time generating a key for this prime resulting in a
hang until the client has finished. This could be exploited in a
Denial Of Service attack.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.openssl.org/news/secadv/20180612.txt</url>
<cvename>CVE-2018-0732</cvename>
</references>
<dates>
<discovery>2018-06-12</discovery>
<entry>2018-06-12</entry>
<modified>2018-07-24</modified>
</dates>
</vuln>
<vuln vid="0137167b-6dca-11e8-a671-001999f8d30b">
<topic>asterisk -- PJSIP endpoint presence disclosure when using ACL</topic>
<affects>
<package>
<name>asterisk13</name>
<range><lt>13.21.1</lt></range>
</package>
<package>
<name>asterisk15</name>
<range><lt>15.4.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Asterisk project reports:</p>
<blockquote cite="http://www.asterisk.org/downloads/security-advisories">
<p> When endpoint specific ACL rules block a SIP request
they respond with a 403 forbidden. However, if an endpoint
is not identified then a 401 unauthorized response is
sent. This vulnerability just discloses which requests
hit a defined endpoint. The ACL rules cannot be bypassed
to gain access to the disclosed endpoints.</p>
</blockquote>
</body>
</description>
<references>
<url>https://downloads.asterisk.org/pub/security/AST-2018-008.html</url>
</references>
<dates>
<discovery>2018-06-11</discovery>
<entry>2018-06-11</entry>
</dates>
</vuln>
<vuln vid="f14ce57f-6dc8-11e8-a671-001999f8d30b">
<topic>asterisk -- Infinite loop when reading iostreams</topic>
<affects>
<package>
<name>asterisk15</name>
<range><lt>15.4.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Asterisk project reports:</p>
<blockquote cite="http://www.asterisk.org/downloads/security-advisories">
<p>When connected to Asterisk via TCP/TLS if the client
abruptly disconnects, or sends a specially crafted message
then Asterisk gets caught in an infinite loop while trying
to read the data stream. Thus rendering the system as
unusable.</p>
</blockquote>
</body>
</description>
<references>
<url>https://downloads.asterisk.org/pub/security/AST-2018-007.html</url>
</references>
<dates>
<discovery>2018-06-11</discovery>
<entry>2018-06-11</entry>
</dates>
</vuln>
<vuln vid="4cb49a23-6c89-11e8-8b33-e8e0b747a45a">
<topic>chromium -- Incorrect handling of CSP header</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>67.0.3396.79</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2018/06/stable-channel-update-for-desktop.html">
<p>1 security fix contributed by external researchers:</p>
<ul>
<li>[845961] High CVE-2018-6148: Incorrect handling of CSP header. Reported by Michal Bentkowski on 2018-05-23</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-6148</cvename>
<url>https://chromereleases.googleblog.com/2018/06/stable-channel-update-for-desktop.html</url>
</references>
<dates>
<discovery>2018-06-06</discovery>
<entry>2018-06-10</entry>
</dates>
</vuln>
<vuln vid="7da0417f-6b24-11e8-84cc-002590acae31">
<topic>gnupg -- unsanitized output (CVE-2018-12020)</topic>
<affects>
<package>
<name>gnupg</name>
<range><lt>2.2.8</lt></range>
</package>
<package>
<name>gnupg1</name>
<range><lt>1.4.23</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GnuPG reports:</p>
<blockquote cite="https://lists.gnupg.org/pipermail/gnupg-announce/2018q2/000425.html">
<p>GnuPG did not sanitize input file names, which may then be output to
the terminal. This could allow terminal control sequences or fake
status messages to be injected into the output.</p>
</blockquote>
</body>
</description>
<references>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12020</url>
<cvename>CVE-2018-12020</cvename>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7526</url>
<cvename>CVE-2017-7526</cvename>
</references>
<dates>
<discovery>2018-06-07</discovery>
<entry>2018-06-08</entry>
</dates>
</vuln>
<vuln vid="e3e68fe8-d9cb-4ba8-b09c-9e3a28588eb7">
<topic>firefox -- Heap buffer overflow rasterizing paths in SVG with Skia</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>60.0.2,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.2.0.13_5</lt></range>
</package>
<package>
<name>firefox-esr</name>
<range><lt>52.8.1,1</lt></range>
</package>
<package>
<name>seamonkey</name>
<name>linux-seamonkey</name>
<range><lt>2.49.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-14/">
<p>A heap buffer overflow can occur in the Skia library when
rasterizing paths using a maliciously crafted SVG file
with anti-aliasing turned off. This results in a
potentially exploitable crash.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.mozilla.org/security/advisories/mfsa2018-14/</url>
</references>
<dates>
<discovery>2018-06-06</discovery>
<entry>2018-06-08</entry>
</dates>
</vuln>
<vuln vid="2dde5a56-6ab1-11e8-b639-6451062f0f7a">
<topic>Flash Player -- multiple vulnerabilities</topic>
<affects>
<package>
<name>linux-flashplayer</name>
<range><lt>30.0.0.113</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Adobe reports:</p>
<blockquote cite="https://helpx.adobe.com/security/products/flash-player/apsb18-19.html">
<ul>
<li>This update resolves a type confusion vulnerability that
could lead to arbitrary code execution (CVE-2018-4945).</li>
<li>This update resolves an integer overflow vulnerability that
could lead to information disclosure (CVE-2018-5000).</li>
<li>This update resolves an out-of-bounds read vulnerability that
could lead to information disclosure (CVE-2018-5001).</li>
<li>This update resolves a stack-based buffer overflow vulnerability that
could lead to arbitrary code execution (CVE-2018-5002).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-4945</cvename>
<cvename>CVE-2018-5000</cvename>
<cvename>CVE-2018-5001</cvename>
<cvename>CVE-2018-5002</cvename>
<url>https://helpx.adobe.com/security/products/flash-player/apsb18-19.html</url>
</references>
<dates>
<discovery>2018-06-07</discovery>
<entry>2018-06-07</entry>
<modified>2018-07-11</modified>
</dates>
</vuln>
<vuln vid="2f4fd3aa-32f8-4116-92f2-68f05398348e">
<topic>bro -- multiple memory allocation issues</topic>
<affects>
<package>
<name>bro</name>
<range><lt>2.5.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Corelight reports:</p>
<blockquote cite="https://www.bro.org/download/NEWS.bro.html">
<p>Bro 2.5.4 primarily fixes security issues</p>
<p>Multiple fixes and improvements to BinPAC generated code related to array parsing, with potential impact to all Bro's BinPAC-generated analyzers in the form of buffer over-reads or other invalid memory accesses depending on whether a particular analyzer incorrectly assumed that the evaulated-array-length expression is actually the number of elements that were parsed out from the input.</p>
<p>The NCP analyzer (not enabled by default and also updated to actually work with newer Bro APIs in the release) performed a memory allocation based directly on a field in the input packet and using signed integer storage. This could result in a signed integer overflow and memory allocations of negative or very large size, leading to a crash or memory exhaustion. The new NCP::max_frame_size tuning option now limits the maximum amount of memory that can be allocated.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.bro.org/download/NEWS.bro.html</url>
</references>
<dates>
<discovery>2018-05-29</discovery>
<entry>2018-06-06</entry>
</dates>
</vuln>
<vuln vid="5a1589ad-68f9-11e8-83f5-d8cb8abf62dd">
<topic>Libgit2 -- Fixing insufficient validation of submodule names</topic>
<affects>
<package>
<name>libgit2</name>
<name>py-pygit2</name>
<range><lt>0.27.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Git community reports:</p>
<blockquote cite="https://github.com/libgit2/libgit2/releases/tag/v0.27.1">
<p>Insufficient validation of submodule names</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/libgit2/libgit2/releases/tag/v0.27.1</url>
<cvename>CVE-2018-11235</cvename>
</references>
<dates>
<discovery>2018-05-29</discovery>
<entry>2018-06-05</entry>
</dates>
</vuln>
<vuln vid="c7a135f4-66a4-11e8-9e63-3085a9a47796">
<topic>Git -- Fix memory out-of-bounds and remote code execution vulnerabilities (CVE-2018-11233 and CVE-2018-11235)</topic>
<affects>
<package>
<name>git</name>
<name>git-lite</name>
<range><lt>2.13.7</lt></range>
<range><ge>2.14</ge><lt>2.14.4</lt></range>
<range><ge>2.15</ge><lt>2.15.2</lt></range>
<range><ge>2.16</ge><lt>2.16.4</lt></range>
<range><ge>2.17</ge><lt>2.17.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Git community reports:</p>
<blockquote cite="https://marc.info/?l=git&m=152761328506724&=2">
<ul><li>In affected versions of Git, code to sanity-check pathnames on
NTFS can result in reading out-of-bounds memory.</li>
<li>In affected versions of Git, remote code execution can
occur. With a crafted .gitmodules file, a malicious project can
execute an arbitrary script on a machine that runs "git clone
--recurse-submodules" because submodule "names" are obtained from
this file, and then appended to $GIT_DIR/modules, leading to
directory traversal with "../" in a name. Finally, post-checkout
hooks from a submodule are executed, bypassing the intended design
in which hooks are not obtained from a remote server.</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11233</url>
<cvename>CVE-2018-11233</cvename>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11235</url>
<cvename>CVE-2018-11235</cvename>
</references>
<dates>
<discovery>2018-05-29</discovery>
<entry>2018-06-02</entry>
</dates>
</vuln>
<vuln vid="9557dc72-64da-11e8-bc32-d8cb8abf62dd">
<topic>Gitlab -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab</name>
<range><ge>10.8.0</ge><lt>10.8.2</lt></range>
<range><ge>10.7.0</ge><lt>10.7.5</lt></range>
<range><ge>1.0</ge><lt>10.6.6</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GitLab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/05/29/security-release-gitlab-10-dot-8-dot-2-released/">
<p>Removing public deploy keys regression</p>
<p>Users can update their password without entering current password</p>
<p>Persistent XSS - Selecting users as allowed merge request approvers</p>
<p>Persistent XSS - Multiple locations of user selection drop downs</p>
<p>include directive in .gitlab-ci.yml allows SSRF requests</p>
<p>Permissions issue in Merge Requests Create Service</p>
<p>Arbitrary assignment of project fields using "Import project"</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/05/29/security-release-gitlab-10-dot-8-dot-2-released/</url>
</references>
<dates>
<discovery>2018-05-29</discovery>
<entry>2018-05-31</entry>
</dates>
</vuln>
<vuln vid="7fc3e827-64a5-11e8-aedb-00224d821998">
<topic>strongswan -- Fix Denial-of-Service Vulnerability strongSwan (CVE-2018-10811, CVE-2018-5388)</topic>
<affects>
<package>
<name>strongswan</name>
<range><lt>5.6.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>strongSwan security team reports:</p>
<blockquote cite="https://www.strongswan.org/blog/2018/05/28/strongswan-5.6.3-released.html">
<ul><li>A denial-of-service vulnerability in the IKEv2 key derivation was fixed
if the openssl plugin is used in FIPS mode and HMAC-MD5 is negotiated as
PRF (which is not FIPS-compliant). So this should only affect very specific setups,
but in such configurations all strongSwan versions since 5.0.1 may be affected.</li>
<li>A denial-of-service vulnerability in the stroke plugin was fixed.
When reading a message from the socket the plugin did not check the received length.
Unless a group is configured, root privileges are required to access that socket,
so in the default configuration this shouldn't be an issue, but all strongSwan versions may be affected.
</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://www.strongswan.org/blog/2018/05/28/strongswan-vulnerability-(cve-2018-10811).html</url>
<cvename>CVE-2018-10811</cvename>
<url>https://www.strongswan.org/blog/2018/05/28/strongswan-vulnerability-(cve-2018-5388).html</url>
<cvename>CVE-2018-5388</cvename>
</references>
<dates>
<discovery>2018-05-16</discovery>
<entry>2018-05-31</entry>
</dates>
</vuln>
<vuln vid="427b0f58-644c-11e8-9e1b-e8e0b747a45a">
<topic>chromium -- multiple vulnerabilities</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>67.0.3396.62</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html">
<p>34 security fixes in this release, including:</p>
<ul>
<li>[835639] High CVE-2018-6123: Use after free in Blink. Reported by Looben Yang on 2018-04-22</li>
<li>[840320] High CVE-2018-6124: Type confusion in Blink. Reported by Guang Gong of Alpha Team, Qihoo 360 on 2018-05-07</li>
<li>[818592] High CVE-2018-6125: Overly permissive policy in WebUSB. Reported by Yubico, Inc on 2018-03-05</li>
<li>[844457] High CVE-2018-6126: Heap buffer overflow in Skia. Reported by Ivan Fratric of Google Project Zero on 2018-05-18</li>
<li>[842990] High CVE-2018-6127: Use after free in indexedDB. Reported by Looben Yang on 2018-05-15</li>
<li>[841105] High CVE-2018-6128: uXSS in Chrome on iOS. Reported by Tomasz Bojarski on 2018-05-09</li>
<li>[838672] High CVE-2018-6129: Out of bounds memory access in WebRTC. Reported by Natalie Silvanovich of Google Project Zero on 2018-05-01</li>
<li>[838402] High CVE-2018-6130: Out of bounds memory access in WebRTC. Reported by Natalie Silvanovich of Google Project Zero on 2018-04-30</li>
<li>[826434] High CVE-2018-6131: Incorrect mutability protection in WebAssembly. Reported by Natalie Silvanovich of Google Project Zero on 2018-03-27</li>
<li>[839960] Medium CVE-2018-6132: Use of uninitialized memory in WebRTC. Reported by Ronald E. Crane on 2018-05-04</li>
<li>[817247] Medium CVE-2018-6133: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-02-28</li>
<li>[797465] Medium CVE-2018-6134: Referrer Policy bypass in Blink. Reported by Jun Kokatsu (@shhnjk) on 2017-12-23</li>
<li>[823353] Medium CVE-2018-6135: UI spoofing in Blink. Reported by Jasper Rebane on 2018-03-19</li>
<li>[831943] Medium CVE-2018-6136: Out of bounds memory access in V8. Reported by Peter Wong on 2018-04-12</li>
<li>[835589] Medium CVE-2018-6137: Leak of visited status of page in Blink. Reported by Michael Smith (spinda.net) on 2018-04-21</li>
<li>[810220] Medium CVE-2018-6138: Overly permissive policy in Extensions. Reported by Francois Lajeunesse-Robert on 2018-02-08</li>
<li>[805224] Medium CVE-2018-6139: Restrictions bypass in the debugger extension API. Reported by Rob Wu on 2018-01-24</li>
<li>[798222] Medium CVE-2018-6140: Restrictions bypass in the debugger extension API. Reported by Rob Wu on 2018-01-01</li>
<li>[796107] Medium CVE-2018-6141: Heap buffer overflow in Skia. Reported by Yangkang (@dnpushme) and Wanglu of Qihoo360 Qex Team on 2017-12-19</li>
<li>[837939] Medium CVE-2018-6142: Out of bounds memory access in V8. Reported by Choongwoo Han of Naver Corporation on 2018-04-28</li>
<li>[843022] Medium CVE-2018-6143: Out of bounds memory access in V8. Reported by Guang Gong of Alpha Team, Qihoo 360 on 2018-05-15</li>
<li>[828049] Low CVE-2018-6144: Out of bounds memory access in PDFium. Reported by pdknsk on 2018-04-02</li>
<li>[805924] Low CVE-2018-6145: Incorrect escaping of MathML in Blink. Reported by Masato Kinugawa on 2018-01-25</li>
<li>[818133] Low CVE-2018-6147: Password fields not taking advantage of OS protections in Views. Reported by Michail Pishchagin (Yandex) on 2018-03-02</li>
<li>[847542] Various fixes from internal audits, fuzzing and other initiatives</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-6123</cvename>
<cvename>CVE-2018-6124</cvename>
<cvename>CVE-2018-6125</cvename>
<cvename>CVE-2018-6126</cvename>
<cvename>CVE-2018-6127</cvename>
<cvename>CVE-2018-6128</cvename>
<cvename>CVE-2018-6129</cvename>
<cvename>CVE-2018-6130</cvename>
<cvename>CVE-2018-6131</cvename>
<cvename>CVE-2018-6132</cvename>
<cvename>CVE-2018-6133</cvename>
<cvename>CVE-2018-6134</cvename>
<cvename>CVE-2018-6135</cvename>
<cvename>CVE-2018-6136</cvename>
<cvename>CVE-2018-6137</cvename>
<cvename>CVE-2018-6138</cvename>
<cvename>CVE-2018-6139</cvename>
<cvename>CVE-2018-6140</cvename>
<cvename>CVE-2018-6141</cvename>
<cvename>CVE-2018-6142</cvename>
<cvename>CVE-2018-6143</cvename>
<cvename>CVE-2018-6144</cvename>
<cvename>CVE-2018-6145</cvename>
<cvename>CVE-2018-6147</cvename>
<url>https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html</url>
</references>
<dates>
<discovery>2018-05-29</discovery>
<entry>2018-05-30</entry>
</dates>
</vuln>
<vuln vid="94599fe0-5ca3-11e8-8be1-d05099c0ae8c">
<topic>BIND -- multiple vulnerabilities</topic>
<affects>
<package>
<name>bind912</name>
<range><lt>9.12.1P2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>ISC reports:</p>
<blockquote cite="https://kb.isc.org/article/AA-01602">
<p>An error in zone database reference counting can
lead to an assertion failure if a server which is
running an affected version of BIND attempts
several transfers of a slave zone in quick
succession.</p>
</blockquote>
<blockquote cite="https://kb.isc.org/article/AA-01606">
<p>A problem with the implementation of the new
serve-stale feature in BIND 9.12 can lead to
an assertion failure in rbtdb.c, even when
stale-answer-enable is off. Additionally,
problematic interaction between the serve-stale
feature and NSEC aggressive negative caching can
in some cases cause undesirable behavior from named,
such as a recursion loop or excessive logging.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-5736</cvename>
<cvename>CVE-2018-5737</cvename>
<url>https://kb.isc.org/article/AA-01602</url>
<url>https://kb.isc.org/article/AA-01606</url>
</references>
<dates>
<discovery>2018-05-18</discovery>
<entry>2018-05-21</entry>
</dates>
</vuln>
<vuln vid="04fe6c8d-2a34-4009-a81e-e7a7e759b5d2">
<topic>cURL -- multiple vulnerabilities</topic>
<affects>
<package>
<name>curl</name>
<range><lt>7.60.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>cURL security problems:</p>
<blockquote cite="https://curl.haxx.se/docs/security.html">
<p>CVE-2018-1000300: FTP shutdown response buffer overflow</p>
<p>curl might overflow a heap based memory buffer when closing down an
FTP connection with very long server command replies.</p>
<p>When doing FTP transfers, curl keeps a spare "closure handle" around
internally that will be used when an FTP connection gets shut down
since the original curl easy handle is then already removed.</p>
<p>FTP server response data that gets cached from the original transfer
might then be larger than the default buffer size (16 KB) allocated in
the "closure handle", which can lead to a buffer overwrite. The
contents and size of that overwrite is controllable by the server.</p>
<p>This situation was detected by an assert() in the code, but that was
of course only preventing bad stuff in debug builds. This bug is very
unlikely to trigger with non-malicious servers.</p>
<p>We are not aware of any exploit of this flaw.</p>
<p>CVE-2018-1000301: RTSP bad headers buffer over-read</p>
<p>curl can be tricked into reading data beyond the end of a heap based
buffer used to store downloaded content.</p>
<p>When servers send RTSP responses back to curl, the data starts out
with a set of headers. curl parses that data to separate it into a
number of headers to deal with those appropriately and to find the end
of the headers that signal the start of the "body" part.</p>
<p>The function that splits up the response into headers is called
Curl_http_readwrite_headers() and in situations where it can't find a
single header in the buffer, it might end up leaving a pointer pointing
into the buffer instead of to the start of the buffer which then later
on may lead to an out of buffer read when code assumes that pointer
points to a full buffer size worth of memory to use.</p>
<p>This could potentially lead to information leakage but most likely a
crash/denial of service for applications if a server triggers this flaw.</p>
<p>We are not aware of any exploit of this flaw.</p>
</blockquote>
</body>
</description>
<references>
<url>https://curl.haxx.se/docs/security.html</url>
<url>https://curl.haxx.se/docs/adv_2018-82c2.html</url>
<url>https://curl.haxx.se/docs/adv_2018-b138.html</url>
<cvename>CVE-2018-1000300</cvename>
<cvename>CVE-2018-1000301</cvename>
</references>
<dates>
<discovery>2018-05-16</discovery>
<entry>2018-05-16</entry>
</dates>
</vuln>
<vuln vid="50210bc1-54ef-11e8-95d9-9c5c8e75236a">
<topic>wavpack -- multiple vulnerabilities</topic>
<affects>
<package>
<name>wavpack</name>
<range><lt>5.1.0_1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Sebastian Ramacher reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6767">
<p>A stack-based buffer over-read in the ParseRiffHeaderConfig function of cli/riff.c file of WavPack 5.1.0 allows a remote attacker to cause a denial-of-service attack or possibly have unspecified other impact via a maliciously crafted RF64 file.</p>
</blockquote>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7253">
<p>The ParseDsdiffHeaderConfig function of the cli/dsdiff.c file of WavPack 5.1.0 allows a remote attacker to cause a denial-of-service (heap-based buffer over-read) or possibly overwrite the heap via a maliciously crafted DSDIFF file.</p>
</blockquote>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7254">
<p>The ParseCaffHeaderConfig function of the cli/caff.c file of WavPack 5.1.0 allows a remote attacker to cause a denial-of-service (global buffer over-read), or possibly trigger a buffer overflow or incorrect memory allocation, via a maliciously crafted CAF file.</p>
</blockquote>
<p>Thuan Pham reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10536">
<p>An issue was discovered in WavPack 5.1.0 and earlier. The WAV parser component contains a vulnerability that allows writing to memory because ParseRiffHeaderConfig in riff.c does not reject multiple format chunks.</p>
</blockquote>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10537">
<p>An issue was discovered in WavPack 5.1.0 and earlier. The W64 parser component contains a vulnerability that allows writing to memory because ParseWave64HeaderConfig in wave64.c does not reject multiple format chunks.</p>
</blockquote>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10538">
<p>An issue was discovered in WavPack 5.1.0 and earlier for WAV input. Out-of-bounds writes can occur because ParseRiffHeaderConfig in riff.c does not validate the sizes of unknown chunks before attempting memory allocation, related to a lack of integer-overflow protection within a bytes_to_copy calculation and subsequent malloc call, leading to insufficient memory allocation.</p>
</blockquote>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10539">
<p>An issue was discovered in WavPack 5.1.0 and earlier for DSDiff input. Out-of-bounds writes can occur because ParseDsdiffHeaderConfig in dsdiff.c does not validate the sizes of unknown chunks before attempting memory allocation, related to a lack of integer-overflow protection within a bytes_to_copy calculation and subsequent malloc call, leading to insufficient memory allocation.</p>
</blockquote>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10540">
<p>An issue was discovered in WavPack 5.1.0 and earlier for W64 input. Out-of-bounds writes can occur because ParseWave64HeaderConfig in wave64.c does not validate the sizes of unknown chunks before attempting memory allocation, related to a lack of integer-overflow protection within a bytes_to_copy calculation and subsequent malloc call, leading to insufficient memory allocation.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-6767</cvename>
<cvename>CVE-2018-7253</cvename>
<cvename>CVE-2018-7254</cvename>
<cvename>CVE-2018-10536</cvename>
<cvename>CVE-2018-10537</cvename>
<cvename>CVE-2018-10538</cvename>
<cvename>CVE-2018-10539</cvename>
<cvename>CVE-2018-10540</cvename>
<url>https://www.debian.org/security/2018/dsa-4125</url>
<url>https://www.debian.org/security/2018/dsa-4197</url>
<freebsdpr>228141</freebsdpr>
</references>
<dates>
<discovery>2018-05-09</discovery>
<entry>2018-05-11</entry>
</dates>
</vuln>
<vuln vid="e457978b-5484-11e8-9b85-54ee754af08e">
<topic>chromium -- multiple vulnerabilities</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>66.0.3359.170</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop.html">
<p>4 security fixes in this release:</p>
<ul>
<li>[835887] Critical: Chain leading to sandbox escape.
Reported by Anonymous on 2018-04-23</li>
<li>[836858] High CVE-2018-6121: Privilege Escalation in extensions</li>
<li>[836141] High CVE-2018-6122: Type confusion in V8</li>
<li>[833721] High CVE-2018-6120: Heap buffer overflow in PDFium.
Reported by Zhou Aiting(@zhouat1) of Qihoo 360 Vulcan Team on 2018-04-17</li>
<li>[841841] Various fixes from internal audits, fuzzing and other initiatives</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-6120</cvename>
<cvename>CVE-2018-6121</cvename>
<cvename>CVE-2018-6122</cvename>
<url>https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop.html</url>
</references>
<dates>
<discovery>2018-04-14</discovery>
<entry>2018-05-11</entry>
</dates>
</vuln>
<vuln vid="06ab7724-0fd7-427e-a5ce-fe436302b10c">
<topic>jenkins -- multiple vulnerabilities</topic>
<affects>
<package>
<name>jenkins</name>
<range><le>2.120</le></range>
</package>
<package>
<name>jenkins-lts</name>
<range><le>2.107.2</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Jenkins developers report:</p>
<blockquote cite="https://jenkins.io/security/advisory/2018-05-09/">
<p>The agent to master security subsystem ensures that the Jenkins
master is protected from maliciously configured agents. A path
traversal vulnerability allowed agents to escape whitelisted
directories to read and write to files they should not be able to
access.</p>
<p>Black Duck Hub Plugin's API endpoint was affected by an XML
External Entity (XXE) processing vulnerability. This allowed an
attacker with Overall/Read access to have Jenkins parse a maliciously
crafted file that uses external entities for extraction of secrets
from the Jenkins master, server-side request forgery, or
denial-of-service attacks.</p>
<p>Several other lower severity issues were reported, see reference
url for details.</p>
</blockquote>
</body>
</description>
<references>
<url>https://jenkins.io/security/advisory/2018-05-09/</url>
</references>
<dates>
<discovery>2018-05-09</discovery>
<entry>2018-05-10</entry>
</dates>
</vuln>
<vuln vid="5aefc41e-d304-4ec8-8c82-824f84f08244">
<topic>mozilla -- multiple vulnerabilities</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>60.0,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.1.0_18</lt></range>
</package>
<package>
<name>seamonkey</name>
<name>linux-seamonkey</name>
<range><lt>2.49.4</lt></range>
</package>
<package>
<name>firefox-esr</name>
<range><lt>52.8.0,1</lt></range>
</package>
<package>
<name>linux-firefox</name>
<range><lt>52.8.0,2</lt></range>
</package>
<package>
<name>libxul</name>
<name>thunderbird</name>
<name>linux-thunderbird</name>
<range><lt>52.8.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/">
<p>CVE-2018-5183: Backport critical security fixes in Skia</p>
<p>CVE-2018-5154: Use-after-free with SVG animations and clip paths</p>
<p>CVE-2018-5155: Use-after-free with SVG animations and text paths</p>
<p>CVE-2018-5157: Same-origin bypass of PDF Viewer to view protected PDF files</p>
<p>CVE-2018-5158: Malicious PDF can inject JavaScript into PDF Viewer</p>
<p>CVE-2018-5159: Integer overflow and out-of-bounds write in Skia</p>
<p>CVE-2018-5160: Uninitialized memory use by WebRTC encoder</p>
<p>CVE-2018-5152: WebExtensions information leak through webRequest API</p>
<p>CVE-2018-5153: Out-of-bounds read in mixed content websocket messages</p>
<p>CVE-2018-5163: Replacing cached data in JavaScript Start-up Bytecode Cache</p>
<p>CVE-2018-5164: CSP not applied to all multipart content sent with multipart/x-mixed-replace</p>
<p>CVE-2018-5166: WebExtension host permission bypass through filterReponseData</p>
<p>CVE-2018-5167: Improper linkification of chrome: and javascript: content in web console and JavaScript debugger</p>
<p>CVE-2018-5168: Lightweight themes can be installed without user interaction</p>
<p>CVE-2018-5169: Dragging and dropping link text onto home button can set home page to include chrome pages</p>
<p>CVE-2018-5172: Pasted script from clipboard can run in the Live Bookmarks page or PDF viewer</p>
<p>CVE-2018-5173: File name spoofing of Downloads panel with Unicode characters</p>
<p>CVE-2018-5174: Windows Defender SmartScreen UI runs with less secure behavior for downloaded files in Windows 10 April 2018 Update</p>
<p>CVE-2018-5175: Universal CSP bypass on sites using strict-dynamic in their policies</p>
<p>CVE-2018-5176: JSON Viewer script injection</p>
<p>CVE-2018-5177: Buffer overflow in XSLT during number formatting</p>
<p>CVE-2018-5165: Checkbox for enabling Flash protected mode is inverted in 32-bit Firefox</p>
<p>CVE-2018-5178: Buffer overflow during UTF-8 to Unicode string conversion through legacy extension</p>
<p>CVE-2018-5180: heap-use-after-free in mozilla::WebGLContext::DrawElementsInstanced</p>
<p>CVE-2018-5181: Local file can be displayed in noopener tab through drag and drop of hyperlink</p>
<p>CVE-2018-5182: Local file can be displayed from hyperlink dragged and dropped on addressbar</p>
<p>CVE-2018-5151: Memory safety bugs fixed in Firefox 60</p>
<p>CVE-2018-5150: Memory safety bugs fixed in Firefox 60 and Firefox ESR 52.8</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-5150</cvename>
<cvename>CVE-2018-5151</cvename>
<cvename>CVE-2018-5152</cvename>
<cvename>CVE-2018-5153</cvename>
<cvename>CVE-2018-5154</cvename>
<cvename>CVE-2018-5155</cvename>
<cvename>CVE-2018-5157</cvename>
<cvename>CVE-2018-5158</cvename>
<cvename>CVE-2018-5159</cvename>
<cvename>CVE-2018-5160</cvename>
<cvename>CVE-2018-5163</cvename>
<cvename>CVE-2018-5164</cvename>
<cvename>CVE-2018-5165</cvename>
<cvename>CVE-2018-5166</cvename>
<cvename>CVE-2018-5167</cvename>
<cvename>CVE-2018-5168</cvename>
<cvename>CVE-2018-5169</cvename>
<cvename>CVE-2018-5172</cvename>
<cvename>CVE-2018-5173</cvename>
<cvename>CVE-2018-5174</cvename>
<cvename>CVE-2018-5175</cvename>
<cvename>CVE-2018-5176</cvename>
<cvename>CVE-2018-5177</cvename>
<cvename>CVE-2018-5178</cvename>
<cvename>CVE-2018-5180</cvename>
<cvename>CVE-2018-5181</cvename>
<cvename>CVE-2018-5182</cvename>
<cvename>CVE-2018-5183</cvename>
<url>https://www.mozilla.org/security/advisories/mfsa2018-11/</url>
<url>https://www.mozilla.org/security/advisories/mfsa2018-12/</url>
</references>
<dates>
<discovery>2018-05-09</discovery>
<entry>2018-05-09</entry>
</dates>
</vuln>
<vuln vid="5af6378b-bd88-4997-bccc-b9ba2daecdd2">
<topic>kamailio - buffer overflow</topic>
<affects>
<package>
<name>kamailio</name>
<range><lt>5.1.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>A specially crafted REGISTER message with a malformed branch or
From tag triggers an off-by-one heap-based buffer overflow in the
tmx_check_pretran function in modules/tmx/tmx_pretran.c</p>
</body>
</description>
<references>
<cvename>CVE-2018-8828</cvename>
<url>https://www.kamailio.org/w/2018/03/kamailio-security-announcement-tmx-lcr/</url>
<url>https://github.com/EnableSecurity/advisories/tree/master/ES2018-05-kamailio-heap-overflow</url>
</references>
<dates>
<discovery>2018-02-10</discovery>
<entry>2018-05-06</entry>
</dates>
</vuln>
<vuln vid="7b5a8e3b-52cc-11e8-8c7a-9c5c8e75236a">
<topic>wget -- cookie injection vulnerability</topic>
<affects>
<package>
<name>wget</name>
<range><lt>1.19.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Harry Sintonen of F-Secure Corporation reports:</p>
<blockquote cite="https://sintonen.fi/advisories/gnu-wget-cookie-injection.txt">
<p>GNU Wget is susceptible to a malicious web server injecting arbitrary cookies to the cookie jar file.</p>
</blockquote>
</body>
</description>
<references>
<url>https://sintonen.fi/advisories/gnu-wget-cookie-injection.txt</url>
<cvename>CVE-2018-0494</cvename>
<freebsdpr>ports/228071</freebsdpr>
</references>
<dates>
<discovery>2018-04-26</discovery>
<entry>2018-05-08</entry>
</dates>
</vuln>
<vuln vid="9558d49c-534c-11e8-8177-d43d7ef03aa6">
<topic>Flash Player -- arbitrary code execution</topic>
<affects>
<package>
<name>linux-flashplayer</name>
<range><lt>29.0.0.171</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Adobe reports:</p>
<blockquote cite="https://helpx.adobe.com/security/products/flash-player/apsb18-16.html">
<ul>
<li>This update resolves a type confusion vulnerability that
could lead to arbitrary code execution (CVE-2018-4944).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-4944</cvename>
<url>https://helpx.adobe.com/security/products/flash-player/apsb18-16.html</url>
</references>
<dates>
<discovery>2018-05-08</discovery>
<entry>2018-05-09</entry>
</dates>
</vuln>
<vuln vid="521ce804-52fd-11e8-9123-a4badb2f4699">
<topic>FreeBSD -- Mishandling of x86 debug exceptions</topic>
<affects>
<package>
<name>FreeBSD-kernel</name>
<range><ge>11.1</ge><lt>11.1_10</lt></range>
<range><ge>10.4</ge><lt>10.4_9</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>The MOV SS and POP SS instructions inhibit debug exceptions
until the instruction boundary following the next instruction.
If that instruction is a system call or similar instruction
that transfers control to the operating system, the debug
exception will be handled in the kernel context instead of
the user context.</p>
<h1>Impact:</h1>
<p>An authenticated local attacker may be able to read
sensitive data in kernel memory, control low-level operating
system functions, or may panic the system.</p>
</body>
</description>
<references>
<cvename>CVE-2018-8897</cvename>
<freebsdsa>SA-18:06.debugreg</freebsdsa>
</references>
<dates>
<discovery>2018-05-08</discovery>
<entry>2018-05-08</entry>
</dates>
</vuln>
<vuln vid="8719b935-8bae-41ad-92ba-3c826f651219">
<topic>python 2.7 -- multiple vulnerabilities</topic>
<affects>
<package>
<name>python27</name>
<range><lt>2.7.15</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>python release notes:</p>
<blockquote cite="https://github.com/python/cpython/blob/2.7/Misc/NEWS.d/2.7.15rc1.rst">
<p>Multiple vulnerabilities has been fixed in this release. Please refer to the CVE list for details.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/python/cpython/blob/2.7/Misc/NEWS.d/2.7.15rc1.rst</url>
<url>https://github.com/python/cpython/blob/2.7/Misc/NEWS.d/2.7.15.rst</url>
<cvename>CVE-2012-0876</cvename>
<cvename>CVE-2016-0718</cvename>
<cvename>CVE-2016-4472</cvename>
<cvename>CVE-2016-9063</cvename>
<cvename>CVE-2017-9233</cvename>
<cvename>CVE-2018-1060</cvename>
<cvename>CVE-2018-1061</cvename>
</references>
<dates>
<discovery>2018-05-01</discovery>
<entry>2018-05-05</entry>
</dates>
</vuln>
<vuln vid="83a548b5-4fa5-11e8-9a8e-001e2a3f778d">
<topic>KWallet-PAM -- Access to privileged files</topic>
<affects>
<package>
<name>plasma5-kwallet-pam</name>
<range><lt>5.12.5_1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The KDE Community reports:</p>
<blockquote cite="https://www.kde.org/info/security/advisory-20180503-1.txt">
<p>
kwallet-pam was doing file writing and permission changing
as root that with correct timing and use of carefully
crafted symbolic links could allow a non privileged user
to become the owner of any file on the system.
</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.kde.org/info/security/advisory-20180503-1.txt</url>
</references>
<dates>
<discovery>2018-05-04</discovery>
<entry>2018-05-04</entry>
</dates>
</vuln>
<vuln vid="89ca6f7d-4f00-11e8-9b1d-00e04c1ea73d">
<topic>drupal -- Drupal Core - Multiple Vulnerabilities</topic>
<affects>
<package>
<name>drupal7</name>
<range><lt>7.58</lt></range>
</package>
<package>
<name>drupal8</name>
<range><lt>8.5.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Drupal Security Team reports:</p>
<blockquote cite="https://www.drupal.org/SA-CORE-2018-004">
<p>A remote code execution vulnerability exists within multiple subsystems of Drupal 7.x and 8.x.
This potentially allows attackers to exploit multiple attack vectors on a Drupal site,
which could result in the site being compromised. This vulnerability is related to
Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-002.
Both SA-CORE-2018-002 and this vulnerability are being exploited in the wild.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.drupal.org/SA-CORE-2018-004</url>
</references>
<dates>
<discovery>2018-04-25</discovery>
<entry>2018-05-03</entry>
</dates>
</vuln>
<vuln vid="9dfe61c8-4d15-11e8-8f2f-d8cb8abf62dd">
<topic>Gitlab -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab</name>
<range><ge>10.7.0</ge><lt>10.7.2</lt></range>
<range><ge>10.6.0</ge><lt>10.6.5</lt></range>
<range><ge>9.5.0</ge><lt>10.5.8</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GitLab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/04/30/security-release-gitlab-10-dot-7-dot-2-released">
<p>Persistent XSS in Move Issue using project namespace</p>
<p>Download Archive allowing unauthorized private repo access</p>
<p>Mattermost Updates</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-10379</cvename>
<url>https://about.gitlab.com/2018/04/30/security-release-gitlab-10-dot-7-dot-2-released</url>
</references>
<dates>
<discovery>2018-04-30</discovery>
<entry>2018-05-01</entry>
</dates>
</vuln>
<vuln vid="006bee4e-4c49-11e8-9c32-54ee754af08e">
<topic>chromium -- vulnerability</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>66.0.3359.139</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop_26.html">
<p>3 security fixes in this release:</p>
<ul>
<li>[831963] Critical CVE-2018-6118: Use after free in Media Cache. Reported by Ned Williamson on 2018-04-12</li>
<li>[837635] Various fixes from internal audits, fuzzing and other initiatives</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-6118</cvename>
<url>https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop_26.html</url>
</references>
<dates>
<discovery>2018-04-12</discovery>
<entry>2018-04-30</entry>
</dates>
</vuln>
<vuln vid="499f6b41-58db-4f98-b8e7-da8c18985eda">
<topic>quassel -- multiple vulnerabilities</topic>
<affects>
<package>
<name>quassel</name>
<range><lt>0.12.5</lt></range>
</package>
<package>
<name>quassel-core</name>
<range><lt>0.12.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gentoo reports:</p>
<blockquote cite="https://bugs.gentoo.org/653834">
<p>quasselcore: corruption of heap metadata caused by qdatastream
leading to preauth remote code execution.</p>
<ul>
<li>Severity: high, by default the server port is publicly open
and the address can be requested using the /WHOIS command of IRC
protocol.</li>
<li>Description: In Qdatastream protocol each object is prepended
with 4 bytes for the object size, this can be used to trigger
allocation errors.</li>
</ul>
<p>quasselcore DDOS</p>
<ul>
<li>Severity: low, only impacts unconfigured quasselcore
instances.</li>
<li>Description: A login attempt causes a NULL pointer dereference
when the database is not initialized.</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://bugs.gentoo.org/653834</url>
<url>https://github.com/quassel/quassel/commit/08bace4e9ecf08273f094c0c6aa8b3363d38ac3e</url>
<url>https://github.com/quassel/quassel/commit/18389a713a6810f57ab237b945e8ee03df857b8b</url>
</references>
<dates>
<discovery>2018-04-24</discovery>
<entry>2018-04-26</entry>
</dates>
</vuln>
<vuln vid="36ff7a74-47b1-11e8-a7d6-54e1ad544088">
<topic>chromium -- vulnerability</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>66.0.3359.117</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html">
<p>62 security fixes in this release:</p>
<ul>
<li>[826626] Critical CVE-2018-6085: Use after free in Disk Cache. Reported by Ned Williamson on 2018-03-28</li>
<li>[827492] Critical CVE-2018-6086: Use after free in Disk Cache. Reported by Ned Williamson on 2018-03-30</li>
<li>[813876] High CVE-2018-6087: Use after free in WebAssembly. Reported by Anonymous on 2018-02-20</li>
<li>[822091] High CVE-2018-6088: Use after free in PDFium. Reported by Anonymous on 2018-03-15</li>
<li>[808838] High CVE-2018-6089: Same origin policy bypass in Service Worker. Reported by Rob Wu on 2018-02-04</li>
<li>[820913] High CVE-2018-6090: Heap buffer overflow in Skia. Reported by ZhanJia Song on 2018-03-12</li>
<li>[771933] High CVE-2018-6091: Incorrect handling of plug-ins by Service Worker. Reported by Jun Kokatsu (@shhnjk) on 2017-10-05</li>
<li>[819869] High CVE-2018-6092: Integer overflow in WebAssembly. Reported by Natalie Silvanovich of Google Project Zero on 2018-03-08</li>
<li>[780435] Medium CVE-2018-6093: Same origin bypass in Service Worker. Reported by Jun Kokatsu (@shhnjk) on 2017-11-01</li>
<li>[633030] Medium CVE-2018-6094: Exploit hardening regression in Oilpan. Reported by Chris Rohlf on 2016-08-01</li>
<li>[637098] Medium CVE-2018-6095: Lack of meaningful user interaction requirement before file upload. Reported by Abdulrahman Alqabandi (@qab) on 2016-08-11</li>
<li>[776418] Medium CVE-2018-6096: Fullscreen UI spoof. Reported by WenXu Wu of Tencent's Xuanwu Lab on 2017-10-19</li>
<li>[806162] Medium CVE-2018-6097: Fullscreen UI spoof. Reported by xisigr of Tencent's Xuanwu Lab on 2018-01-26</li>
<li>[798892] Medium CVE-2018-6098: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-01-03</li>
<li>[808825] Medium CVE-2018-6099: CORS bypass in ServiceWorker. Reported by Jun Kokatsu (@shhnjk) on 2018-02-03</li>
<li>[811117] Medium CVE-2018-6100: URL spoof in Omnibox. Reported by Lnyas Zhang on 2018-02-11</li>
<li>[813540] Medium CVE-2018-6101: Insufficient protection of remote debugging prototol in DevTools . Reported by Rob Wu on 2018-02-19</li>
<li>[813814] Medium CVE-2018-6102: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-02-20</li>
<li>[816033] Medium CVE-2018-6103: UI spoof in Permissions. Reported by Khalil Zhani on 2018-02-24</li>
<li>[820068] Medium CVE-2018-6104: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-03-08</li>
<li>[803571] Medium CVE-2018-6105: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-01-18</li>
<li>[805729] Medium CVE-2018-6106: Incorrect handling of promises in V8. Reported by lokihardt of Google Project Zero on 2018-01-25</li>
<li>[808316] Medium CVE-2018-6107: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-02-02</li>
<li>[816769] Medium CVE-2018-6108: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-02-27</li>
<li>[710190] Low CVE-2018-6109: Incorrect handling of files by FileAPI. Reported by Dominik Weber (@DoWeb_) on 2017-04-10</li>
<li>[777737] Low CVE-2018-6110: Incorrect handling of plaintext files via file:// . Reported by Wenxiang Qian (aka blastxiang) on 2017-10-24</li>
<li>[780694] Low CVE-2018-6111: Heap-use-after-free in DevTools. Reported by Khalil Zhani on 2017-11-02</li>
<li>[798096] Low CVE-2018-6112: Incorrect URL handling in DevTools. Reported by Rob Wu on 2017-12-29</li>
<li>[805900] Low CVE-2018-6113: URL spoof in Navigation. Reported by Khalil Zhani on 2018-01-25</li>
<li>[811691] Low CVE-2018-6114: CSP bypass. Reported by Lnyas Zhang on 2018-02-13</li>
<li>[819809] Low CVE-2018-6115: SmartScreen bypass in downloads. Reported by James Feher on 2018-03-07</li>
<li>[822266] Low CVE-2018-6116: Incorrect low memory handling in WebAssembly. Reported by Jin from Chengdu Security Response Center of Qihoo 360 Technology Co. Ltd. on 2018-03-15</li>
<li>[822465] Low CVE-2018-6117: Confusing autofill settings. Reported by Spencer Dailey on 2018-03-15</li>
<li>[822424] Low CVE-2018-6084: Incorrect use of Distributed Objects in Google Software Updater on MacOS. Reported by Ian Beer of Google Project Zero on 2018-03-15</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html</url>
<cvename>CVE-2018-6085</cvename>
<cvename>CVE-2018-6086</cvename>
<cvename>CVE-2018-6087</cvename>
<cvename>CVE-2018-6088</cvename>
<cvename>CVE-2018-6089</cvename>
<cvename>CVE-2018-6090</cvename>
<cvename>CVE-2018-6091</cvename>
<cvename>CVE-2018-6092</cvename>
<cvename>CVE-2018-6093</cvename>
<cvename>CVE-2018-6094</cvename>
<cvename>CVE-2018-6095</cvename>
<cvename>CVE-2018-6096</cvename>
<cvename>CVE-2018-6097</cvename>
<cvename>CVE-2018-6098</cvename>
<cvename>CVE-2018-6099</cvename>
<cvename>CVE-2018-6100</cvename>
<cvename>CVE-2018-6101</cvename>
<cvename>CVE-2018-6102</cvename>
<cvename>CVE-2018-6103</cvename>
<cvename>CVE-2018-6104</cvename>
<cvename>CVE-2018-6105</cvename>
<cvename>CVE-2018-6106</cvename>
<cvename>CVE-2018-6107</cvename>
<cvename>CVE-2018-6108</cvename>
<cvename>CVE-2018-6109</cvename>
<cvename>CVE-2018-6110</cvename>
<cvename>CVE-2018-6111</cvename>
<cvename>CVE-2018-6112</cvename>
<cvename>CVE-2018-6113</cvename>
<cvename>CVE-2018-6114</cvename>
<cvename>CVE-2018-6115</cvename>
<cvename>CVE-2018-6116</cvename>
<cvename>CVE-2018-6117</cvename>
<cvename>CVE-2018-6084</cvename>
</references>
<dates>
<discovery>2017-04-10</discovery>
<entry>2018-04-24</entry>
</dates>
</vuln>
<vuln vid="d8382a69-4728-11e8-ba83-0011d823eebd">
<topic>mbed TLS (PolarSSL) -- multiple vulnerabilities</topic>
<affects>
<package>
<name>mbedtls</name>
<range><lt>2.7.2</lt></range>
</package>
<package>
<name>polarssl13</name>
<range><ge>*</ge></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Simon Butcher reports:</p>
<blockquote cite="https://tls.mbed.org/tech-updates/releases/mbedtls-2.8.0-2.7.2-and-2.1.11-released">
<ul>
<li>Defend against Bellcore glitch attacks by verifying the results
of RSA private key operations.</li>
<li>Fix implementation of the truncated HMAC extension. The
previous implementation allowed an offline 2^80 brute force
attack on the HMAC key of a single, uninterrupted connection
(with no resumption of the session).</li>
<li>Reject CRLs containing unsupported critical extensions. Found
by Falko Strenzke and Evangelos Karatsiolis.</li>
<li>Fix a buffer overread in ssl_parse_server_key_exchange() that
could cause a crash on invalid input.</li>
<li>Fix a buffer overread in ssl_parse_server_psk_hint() that could
cause a crash on invalid input.</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://tls.mbed.org/tech-updates/releases/mbedtls-2.8.0-2.7.2-and-2.1.11-released</url>
</references>
<dates>
<discovery>2018-03-21</discovery>
<entry>2018-04-23</entry>
</dates>
</vuln>
<vuln vid="57aec168-453e-11e8-8777-b499baebfeaf">
<topic>MySQL -- multiple vulnerabilities</topic>
<affects>
<package>
<name>mariadb55-server</name>
<range><lt>5.5.60</lt></range>
</package>
<package>
<name>mariadb100-server</name>
<range><lt>10.0.35</lt></range>
</package>
<package>
<name>mariadb101-server</name>
<range><lt>10.1.33</lt></range>
</package>
<package>
<name>mariadb102-server</name>
<range><lt>10.2.15</lt></range>
</package>
<package>
<name>mysql55-server</name>
<range><lt>5.5.60</lt></range>
</package>
<package>
<name>mysql56-server</name>
<range><lt>5.6.40</lt></range>
</package>
<package>
<name>mysql57-server</name>
<range><lt>5.7.22</lt></range>
</package>
<package>
<name>percona55-server</name>
<range><lt>5.5.60</lt></range>
</package>
<package>
<name>percona56-server</name>
<range><lt>5.6.40</lt></range>
</package>
<package>
<name>percona57-server</name>
<range><lt>5.7.22</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Oracle reports:</p>
<blockquote cite="http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html">
<p>MySQL Multiple Flaws Let Remote Authenticated Users Access and
Modify Data, Remote and Local Users Deny Service, and Local Users
Access Data and Gain Elevated Privileges</p>
<ul>
<li>A local user can exploit a flaw in the Replication component
to gain elevated privileges [CVE-2018-2755].</li>
<li>A remote authenticated user can exploit a flaw in the GIS
Extension component to cause denial of service conditions
[CVE-2018-2805].</li>
<li>A remote authenticated user can exploit a flaw in the InnoDB
component to cause denial of service conditions [CVE-2018-2782,
CVE-2018-2784, CVE-2018-2819].</li>
<li>A remote authenticated user can exploit a flaw in the Security
Privileges component to cause denial of service conditions
[CVE-2018-2758, CVE-2018-2818].</li>
<li>A remote authenticated user can exploit a flaw in the DDL
component to cause denial of service conditions
[CVE-2018-2817].</li>
<li>A remote authenticated user can exploit a flaw in the Optimizer
component to cause denial of service conditions [CVE-2018-2775,
CVE-2018-2778, CVE-2018-2779, CVE-2018-2780, CVE-2018-2781,
CVE-2018-2816].</li>
<li>A remote user can exploit a flaw in the Client programs
component to cause denial of service conditions [CVE-2018-2761,
CVE-2018-2773].</li>
<li>A remote authenticated user can exploit a flaw in the InnoDB
component to partially modify data and cause denial of service
conditions [CVE-2018-2786, CVE-2018-2787].</li>
<li>A remote authenticated user can exploit a flaw in the Optimizer
component to partially modify data and cause denial of service
conditions [CVE-2018-2812].</li>
<li>A local user can exploit a flaw in the Cluster ndbcluster/plugin
component to cause denial of service conditions [CVE-2018-2877].
</li>
<li>A remote authenticated user can exploit a flaw in the InnoDB
component to cause denial of service conditions [CVE-2018-2759,
CVE-2018-2766, CVE-2018-2777, CVE-2018-2810].</li>
<li>A remote authenticated user can exploit a flaw in the DML
component to cause denial of service conditions [CVE-2018-2839].
</li>
<li>A remote authenticated user can exploit a flaw in the
Performance Schema component to cause denial of service conditions
[CVE-2018-2846].</li>
<li>A remote authenticated user can exploit a flaw in the Pluggable
Auth component to cause denial of service conditions
[CVE-2018-2769].</li>
<li>A remote authenticated user can exploit a flaw in the Group
Replication GCS component to cause denial of service conditions
[CVE-2018-2776].</li>
<li>A local user can exploit a flaw in the Connection component to
cause denial of service conditions [CVE-2018-2762].</li>
<li>A remote authenticated user can exploit a flaw in the Locking
component to cause denial of service conditions [CVE-2018-2771].
</li>
<li>A remote authenticated user can exploit a flaw in the DDL
component to partially access data [CVE-2018-2813].</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html</url>
<cvename>CVE-2018-2755</cvename>
<cvename>CVE-2018-2805</cvename>
<cvename>CVE-2018-2782</cvename>
<cvename>CVE-2018-2784</cvename>
<cvename>CVE-2018-2819</cvename>
<cvename>CVE-2018-2758</cvename>
<cvename>CVE-2018-2817</cvename>
<cvename>CVE-2018-2775</cvename>
<cvename>CVE-2018-2780</cvename>
<cvename>CVE-2018-2761</cvename>
<cvename>CVE-2018-2786</cvename>
<cvename>CVE-2018-2787</cvename>
<cvename>CVE-2018-2812</cvename>
<cvename>CVE-2018-2877</cvename>
<cvename>CVE-2018-2759</cvename>
<cvename>CVE-2018-2766</cvename>
<cvename>CVE-2018-2777</cvename>
<cvename>CVE-2018-2810</cvename>
<cvename>CVE-2018-2818</cvename>
<cvename>CVE-2018-2839</cvename>
<cvename>CVE-2018-2778</cvename>
<cvename>CVE-2018-2779</cvename>
<cvename>CVE-2018-2781</cvename>
<cvename>CVE-2018-2816</cvename>
<cvename>CVE-2018-2846</cvename>
<cvename>CVE-2018-2769</cvename>
<cvename>CVE-2018-2776</cvename>
<cvename>CVE-2018-2762</cvename>
<cvename>CVE-2018-2771</cvename>
<cvename>CVE-2018-2813</cvename>
<cvename>CVE-2018-2773</cvename>
</references>
<dates>
<discovery>2018-04-17</discovery>
<entry>2018-04-21</entry>
</dates>
</vuln>
<vuln vid="be38245e-44d9-11e8-a292-00e04c1ea73d">
<topic>wordpress -- multiple issues</topic>
<affects>
<package>
<name>wordpress</name>
<name>fr-wordpress</name>
<range><lt>4.9.5,1</lt></range>
</package>
<package>
<name>de-wordpress</name>
<name>zh_CN-wordpress</name>
<name>zh_TW-wordpress</name>
<name>ja-wordpress</name>
<range><lt>4.9.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>wordpress developers reports:</p>
<blockquote cite="https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/">
<p>Don't treat localhost as same host by default.</p>
<p>Use safe redirects when redirecting the login page if SSL is forced.</p>
<p>Make sure the version string is correctly escaped for use in generator tags.</p>
</blockquote>
</body>
</description>
<references>
<url>https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/</url>
</references>
<dates>
<discovery>2018-04-03</discovery>
<entry>2018-04-20</entry>
</dates>
</vuln>
<vuln vid="ac7da39b-4405-11e8-afbe-6805ca0b3d42">
<topic>phpmyadmin -- CSRF vulnerability allowing arbitrary SQL execution</topic>
<affects>
<package>
<name>phpmyadmin</name>
<range><ge>4.8.0</ge><lt>4.8.0.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The phpMyAdmin development team reports:</p>
<blockquote cite="https://www.phpmyadmin.net/security/PMASA-2018-2/">
<h3>Summary</h3>
<p>CSRF vulnerability allowing arbitrary SQL execution</p>
<h3>Description</h3>
<p>By deceiving a user to click on a crafted URL, it is
possible for an attacker to execute arbitrary SQL
commands.</p>
<h3>Severity</h3>
<p>We consider this vulnerability to be critical.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.phpmyadmin.net/security/PMASA-2018-2/</url>
</references>
<dates>
<discovery>2018-04-17</discovery>
<entry>2018-04-19</entry>
</dates>
</vuln>
<vuln vid="33174280-43fa-11e8-aad5-6cf0497db129">
<topic>drupal -- Drupal core - Moderately critical</topic>
<affects>
<package>
<name>drupal8</name>
<range><lt>8.5.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Drupal security team reports:</p>
<blockquote cite="https://www.drupal.org/sa-core-2018-003">
<p>CKEditor, a third-party JavaScript library included in Drupal
core, has fixed a cross-site scripting (XSS) vulnerability. The
vulnerability stemmed from the fact that it was possible to execute
XSS inside CKEditor when using the image2 plugin (which Drupal 8
core also uses).</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.drupal.org/sa-core-2018-003</url>
</references>
<dates>
<discovery>2018-04-18</discovery>
<entry>2018-04-19</entry>
</dates>
</vuln>
<vuln vid="8f353420-4197-11e8-8777-b499baebfeaf">
<topic>OpenSSL -- Cache timing vulnerability</topic>
<affects>
<package>
<name>openssl</name>
<range><lt>1.0.2o_2,1</lt></range>
</package>
<package>
<name>openssl-devel</name>
<range><lt>1.1.0h_1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The OpenSSL project reports:</p>
<blockquote cite="https://www.openssl.org/news/secadv/20180416.txt">
<p>The OpenSSL RSA Key generation algorithm has been shown to be
vulnerable to a cache timing side channel attack. An attacker
with sufficient access to mount cache timing attacks during the
RSA key generation process could recover the private key.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.openssl.org/news/secadv/20180416.txt</url>
<cvename>CVE-2018-0737</cvename>
</references>
<dates>
<discovery>2018-04-16</discovery>
<entry>2018-04-16</entry>
</dates>
</vuln>
<vuln vid="a9e466e8-4144-11e8-a292-00e04c1ea73d">
<topic>drupal -- Drupal Core - Multiple Vulnerabilities</topic>
<affects>
<package>
<name>drupal7</name>
<range><lt>7.57</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Drupal Security Team reports:</p>
<blockquote cite="https://www.drupal.org/psa-2018-001">
<p>CVE-2018-7600: Drupal before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6,
and 8.5.x before 8.5.1 allows remote attackers to execute arbitrary code because
of an issue affecting multiple subsystems with default or common module configurations.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-7600</cvename>
</references>
<dates>
<discovery>2018-03-13</discovery>
<entry>2018-04-16</entry>
</dates>
</vuln>
<vuln vid="41c96ffd-29a6-4dcc-9a88-65f5038fa6eb">
<topic>perl -- multiple vulnerabilities</topic>
<affects>
<package>
<name>perl5</name>
<range><ge>5.24.0</ge><lt>5.24.4</lt></range>
<range><ge>5.26.0</ge><lt>5.26.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>perldelta:</p>
<blockquote cite="https://metacpan.org/changes/release/SHAY/perl-5.26.2">
<p>CVE-2018-6797: heap-buffer-overflow (WRITE of size 1) in S_regatom
(regcomp.c)</p>
<p>A crafted regular expression could cause a heap buffer write overflow,
with control over the bytes written. [perl #132227]</p>
<p>CVE-2018-6798: Heap-buffer-overflow in Perl__byte_dump_string (utf8.c)</p>
<p>Matching a crafted locale dependent regular expression could cause a
heap buffer read overflow and potentially information disclosure. [perl
#132063]</p>
<p>CVE-2018-6913: heap-buffer-overflow in S_pack_rec</p>
<p>pack() could cause a heap buffer write overflow with a large item
count. [perl #131844]</p>
</blockquote>
</body>
</description>
<references>
<url>https://metacpan.org/changes/release/SHAY/perl-5.26.2</url>
<url>https://metacpan.org/changes/release/SHAY/perl-5.24.4</url>
<cvename>CVE-2018-6797</cvename>
<cvename>CVE-2018-6798</cvename>
<cvename>CVE-2018-6913</cvename>
</references>
<dates>
<discovery>2018-04-14</discovery>
<entry>2018-04-15</entry>
</dates>
</vuln>
<vuln vid="974a6d32-3fda-11e8-aea4-001b216d295b">
<topic>ipsec-tools -- remotely exploitable computational-complexity attack</topic>
<affects>
<package>
<name>ipsec-tools</name>
<range><lt>0.8.2_3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Robert Foggia via NetBSD GNATS reports:</p>
<blockquote cite="https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=51682">
<p>The ipsec-tools racoon daemon contains a remotely exploitable computational
complexity attack when parsing and storing isakmp fragments. The implementation
permits a remote attacker to exhaust computational resources on the remote endpoint
by repeatedly sending isakmp fragment packets in a particular order such that
the worst-case computational complexity is realized in the algorithm utilized
to determine if reassembly of the fragments can take place.</p>
</blockquote>
</body>
</description>
<references>
<url>https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=51682</url>
<cvename>CVE-2016-10396</cvename>
</references>
<dates>
<discovery>2016-12-02</discovery>
<entry>2018-04-14</entry>
</dates>
</vuln>
<vuln vid="1fccb25e-8451-438c-a2b9-6a021e4d7a31">
<topic>nghttp2 -- Denial of service due to NULL pointer dereference</topic>
<affects>
<package>
<name>libnghttp2</name>
<name>nghttp2</name>
<range><ge>1.10.0</ge><lt>1.31.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>nghttp2 blog:</p>
<blockquote cite="https://nghttp2.org/blog/2018/04/12/nghttp2-v1-31-1/">
<p>If ALTSVC frame is received by libnghttp2 and it is larger than it can
accept, the pointer field which points to ALTSVC frame payload is left
NULL. Later libnghttp2 attempts to access another field through the
pointer, and gets segmentation fault.</p>
<p>ALTSVC frame is defined by RFC 7838.</p>
<p>The largest frame size libnghttp2 accept is by default 16384 bytes.</p>
<p>Receiving ALTSVC frame is disabled by default. Application has to
enable it explicitly by calling
nghttp2_option_set_builtin_recv_extension_type(opt, NGHTTP2_ALTSVC).</p>
<p>Transmission of ALTSVC is always enabled, and it does not cause this
vulnerability.</p>
<p>ALTSVC frame is expected to be sent by server, and received by client
as defined in RFC 7838.</p>
<p>Client and server are both affected by this vulnerability if the
reception of ALTSVC frame is enabled. As written earlier, it is useless
to enable reception of ALTSVC frame on server side. So, server is
generally safe unless application accidentally enabled the reception of
ALTSVC frame.</p>
</blockquote>
</body>
</description>
<references>
<url>https://nghttp2.org/blog/2018/04/12/nghttp2-v1-31-1/</url>
<cvename>CVE-2018-1000168</cvename>
</references>
<dates>
<discovery>2018-04-04</discovery>
<entry>2018-04-13</entry>
</dates>
</vuln>
<vuln vid="48894ca9-3e6f-11e8-92f0-f0def167eeea">
<topic>roundcube -- IMAP command injection vulnerability</topic>
<affects>
<package>
<name>roundcube</name>
<range><le>1.3.5,1</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Upstream reports:</p>
<blockquote cite="https://roundcube.net/news/2018/04/11/security-update-1.3.6">
<p>This update primarily fixes a recently discovered IMAP-cmd-injection
vulnerability caused by insufficient input validation within
the archive plugin.
Details about the vulnerability are published under CVE-2018-9846.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-9846</cvename>
<url>https://roundcube.net/news/2018/04/11/security-update-1.3.6</url>
</references>
<dates>
<discovery>2018-04-11</discovery>
<entry>2018-04-13</entry>
</dates>
</vuln>
<vuln vid="aaba17aa-782e-4843-8a79-7756cfa2bf89">
<topic>jenkins -- multiple vulnerabilities</topic>
<affects>
<package>
<name>jenkins</name>
<range><le>2.115</le></range>
</package>
<package>
<name>jenkins-lts</name>
<range><le>2.107.1</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Jenkins developers report:</p>
<blockquote cite="https://jenkins.io/security/advisory/2018-04-11/">
<p>The Jenkins CLI sent different error responses for commands with
view and agent arguments depending on the existence of the specified
views or agents to unauthorized users. This allowed attackers to
determine whether views or agents with specified names exist.</p>
<p>The Jenkins CLI now returns the same error messages to unauthorized
users independent of the existence of specified view or agent
names</p>
<p>Some JavaScript confirmation dialogs included the item name in an
unsafe manner, resulting in a possible cross-site scripting
vulnerability exploitable by users with permission to create or
configure items.</p>
<p>JavaScript confirmation dialogs that include the item name now
properly escape it, so it can be safely displayed.</p>
</blockquote>
</body>
</description>
<references>
<url>https://jenkins.io/security/advisory/2018-04-11/</url>
</references>
<dates>
<discovery>2018-04-11</discovery>
<entry>2018-04-12</entry>
</dates>
</vuln>
<vuln vid="5c6f7482-3ced-11e8-b157-6451062f0f7a">
<topic>Flash Player -- multiple vulnerabilities</topic>
<affects>
<package>
<name>linux-flashplayer</name>
<range><lt>29.0.0.140</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Adobe reports:</p>
<blockquote cite="https://helpx.adobe.com/security/products/flash-player/apsb18-08.html">
<ul>
<li>This update resolves a use-after-free vulnerability that
could lead to remote code execution (CVE-2018-4932).</li>
<li>This update resolves out-of-bounds read vulnerabilities that
could lead to information disclosure (CVE-2018-4933,
CVE-2018-4934).</li>
<li>This update resolves out-of-bounds write vulnerabilities that
could lead to remote code execution (CVE-2018-4935,
CVE-2018-4937).</li>
<li>This update resolves a heap overflow vulnerability that
could lead to information disclosure (CVE-2018-4936).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-4932</cvename>
<cvename>CVE-2018-4933</cvename>
<cvename>CVE-2018-4934</cvename>
<cvename>CVE-2018-4935</cvename>
<cvename>CVE-2018-4936</cvename>
<cvename>CVE-2018-4937</cvename>
<url>https://helpx.adobe.com/security/products/flash-player/apsb18-08.html</url>
</references>
<dates>
<discovery>2018-04-10</discovery>
<entry>2018-04-10</entry>
<modified>2018-07-11</modified>
</dates>
</vuln>
<vuln vid="085a087b-3897-11e8-ac53-d8cb8abf62dd">
<topic>Gitlab -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab</name>
<range><ge>10.6.0</ge><lt>10.6.3</lt></range>
<range><ge>10.5.0</ge><lt>10.5.7</lt></range>
<range><ge>8.6</ge><lt>10.4.7</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GitLab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/04/04/security-release-gitlab-10-dot-6-dot-3-released/">
<p>Confidential issue comments in Slack, Mattermost, and webhook integrations.</p>
<p>Persistent XSS in milestones data-milestone-id.</p>
<p>Persistent XSS in filename of merge request.</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/04/04/security-release-gitlab-10-dot-6-dot-3-released/</url>
</references>
<dates>
<discovery>2018-04-04</discovery>
<entry>2018-04-05</entry>
</dates>
</vuln>
<vuln vid="c0c5afef-38db-11e8-8b7f-a4badb2f469b">
<topic>FreeBSD -- ipsec crash or denial of service</topic>
<affects>
<package>
<name>FreeBSD-kernel</name>
<range><ge>11.1</ge><lt>11.1_9</lt></range>
<range><ge>10.4</ge><lt>10.4_8</lt></range>
<range><ge>10.3</ge><lt>10.3_29</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>The length field of the option header does not count the
size of the option header itself. This causes a problem
when the length is zero, the count is then incremented by
zero, which causes an infinite loop.</p>
<p>In addition there are pointer/offset mistakes in the
handling of IPv4 options.</p>
<h1>Impact:</h1>
<p>A remote attacker who is able to send an arbitrary packet,
could cause the remote target machine to crash.</p>
</body>
</description>
<references>
<cvename>CVE-2018-6918</cvename>
<freebsdsa>SA-18:05.ipsec</freebsdsa>
</references>
<dates>
<discovery>2018-04-04</discovery>
<entry>2018-04-05</entry>
</dates>
</vuln>
<vuln vid="a5cf3ecd-38db-11e8-8b7f-a4badb2f469b">
<topic>FreeBSD -- vt console memory disclosure</topic>
<affects>
<package>
<name>FreeBSD-kernel</name>
<range><ge>11.1</ge><lt>11.1_9</lt></range>
<range><ge>10.4</ge><lt>10.4_8</lt></range>
<range><ge>10.3</ge><lt>10.3_29</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>Insufficient validation of user-provided font parameters
can result in an integer overflow, leading to the use of
arbitrary kernel memory as glyph data. Characters that
reference this data can be displayed on the screen, effectively
disclosing kernel memory.</p>
<h1>Impact:</h1>
<p>Unprivileged users may be able to access privileged
kernel data.</p>
<p>Such memory might contain sensitive information, such
as portions of the file cache or terminal buffers. This
information might be directly useful, or it might be leveraged
to obtain elevated privileges in some way; for example, a
terminal buffer might include a user-entered password.</p>
</body>
</description>
<references>
<cvename>CVE-2018-6917</cvename>
<freebsdsa>SA-18:04.vt</freebsdsa>
</references>
<dates>
<discovery>2018-04-04</discovery>
<entry>2018-04-05</entry>
</dates>
</vuln>
<vuln vid="cdb4d962-34f9-11e8-92db-080027907385">
<topic>moodle -- multiple vulnerabilities</topic>
<affects>
<package>
<name>moodle31</name>
<range><lt>3.1.11</lt></range>
</package>
<package>
<name>moodle32</name>
<range><lt>3.2.8</lt></range>
</package>
<package>
<name>moodle33</name>
<range><lt>3.3.5</lt></range>
</package>
<package>
<name>moodle34</name>
<range><lt>3.4.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>moodle reports:</p>
<blockquote cite="https://moodle.org/mod/forum/discuss.php?d=367938">
<p>Unauthenticated users can trigger custom messages to admin via
paypal enrol script.</p>
<p>Suspended users with OAuth 2 authentication method can still log in to
the site.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-1081</cvename>
<cvename>CVE-2018-1082</cvename>
<url>https://moodle.org/mod/forum/discuss.php?d=367938</url>
</references>
<dates>
<discovery>2018-03-14</discovery>
<entry>2018-03-31</entry>
</dates>
</vuln>
<vuln vid="eb69bcf2-18ef-4aa2-bb0c-83b263364089">
<topic>ruby -- multiple vulnerabilities</topic>
<affects>
<package>
<name>ruby</name>
<range><ge>2.3.0,1</ge><lt>2.3.7,1</lt></range>
<range><ge>2.4.0,1</ge><lt>2.4.4,1</lt></range>
<range><ge>2.5.0,1</ge><lt>2.5.1,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Ruby news:</p>
<blockquote cite="https://www.ruby-lang.org/en/news/2018/03/28/ruby-2-5-1-released/">
<p>CVE-2017-17742: HTTP response splitting in WEBrick</p>
<p>If a script accepts an external input and outputs it without
modification as a part of HTTP responses, an attacker can use newline
characters to deceive the clients that the HTTP response header is
stopped at there, and can inject fake HTTP responses after the newline
characters to show malicious contents to the clients.</p>
<p>CVE-2018-6914: Unintentional file and directory creation with
directory traversal in tempfile and tmpdir</p>
<p>Dir.mktmpdir method introduced by tmpdir library accepts the prefix
and the suffix of the directory which is created as the first parameter.
The prefix can contain relative directory specifiers "../", so this
method can be used to target any directory. So, if a script accepts an
external input as the prefix, and the targeted directory has
inappropriate permissions or the ruby process has inappropriate
privileges, the attacker can create a directory or a file at any
directory.</p>
<p>CVE-2018-8777: DoS by large request in WEBrick</p>
<p>If an attacker sends a large request which contains huge HTTP headers,
WEBrick try to process it on memory, so the request causes the
out-of-memory DoS attack.</p>
<p>CVE-2018-8778: Buffer under-read in String#unpack</p>
<p>String#unpack receives format specifiers as its parameter, and can
be specified the position of parsing the data by the specifier @. If a
big number is passed with @, the number is treated as the negative
value, and out-of-buffer read is occurred. So, if a script accepts an
external input as the argument of String#unpack, the attacker can read
data on heaps.</p>
<p>CVE-2018-8779: Unintentional socket creation by poisoned NUL byte in
UNIXServer and UNIXSocket</p>
<p>UNIXServer.open accepts the path of the socket to be created at the
first parameter. If the path contains NUL (\0) bytes, this method
recognize that the path is completed before the NUL bytes. So, if a
script accepts an external input as the argument of this method, the
attacker can make the socket file in the unintentional path. And,
UNIXSocket.open also accepts the path of the socket to be created at
the first parameter without checking NUL bytes like UNIXServer.open.
So, if a script accepts an external input as the argument of this
method, the attacker can accepts the socket file in the unintentional
path.</p>
<p>CVE-2018-8780: Unintentional directory traversal by poisoned NUL byte
in Dir</p>
<p>Dir.open, Dir.new, Dir.entries and Dir.empty? accept the path of the
target directory as their parameter. If the parameter contains NUL (\0)
bytes, these methods recognize that the path is completed before the
NUL bytes. So, if a script accepts an external input as the argument of
these methods, the attacker can make the unintentional directory
traversal.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.ruby-lang.org/en/news/2018/03/28/ruby-2-5-1-released/</url>
<url>https://www.ruby-lang.org/en/news/2018/03/28/ruby-2-4-4-released/</url>
<url>https://www.ruby-lang.org/en/news/2018/03/28/ruby-2-3-7-released/</url>
<url>https://www.ruby-lang.org/en/news/2018/03/28/http-response-splitting-in-webrick-cve-2017-17742/</url>
<url>https://www.ruby-lang.org/en/news/2018/03/28/unintentional-file-and-directory-creation-with-directory-traversal-cve-2018-6914/</url>
<url>https://www.ruby-lang.org/en/news/2018/03/28/large-request-dos-in-webrick-cve-2018-8777/</url>
<url>https://www.ruby-lang.org/en/news/2018/03/28/buffer-under-read-unpack-cve-2018-8778/</url>
<url>https://www.ruby-lang.org/en/news/2018/03/28/poisoned-nul-byte-unixsocket-cve-2018-8779/</url>
<url>https://www.ruby-lang.org/en/news/2018/03/28/poisoned-nul-byte-dir-cve-2018-8780/</url>
<cvename>CVE-2017-17742</cvename>
<cvename>CVE-2018-6914</cvename>
<cvename>CVE-2018-8777</cvename>
<cvename>CVE-2018-8778</cvename>
<cvename>CVE-2018-8779</cvename>
<cvename>CVE-2018-8780</cvename>
</references>
<dates>
<discovery>2018-03-28</discovery>
<entry>2018-03-29</entry>
</dates>
</vuln>
<vuln vid="5a9bbb6e-32d3-11e8-a769-6daaba161086">
<topic>node.js -- multiple vulnerabilities</topic>
<affects>
<package>
<name>node4</name>
<range><lt>4.9.0</lt></range>
</package>
<package>
<name>node6</name>
<range><lt>6.14.0</lt></range>
</package>
<package>
<name>node8</name>
<range><lt>8.11.0</lt></range>
</package>
<package>
<name>node</name>
<range><lt>9.10.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Node.js reports:</p>
<blockquote cite="https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/">
<h1>Node.js Inspector DNS rebinding vulnerability (CVE-2018-7160)</h1>
<p>Node.js 6.x and later include a debugger protocol (also known as "inspector") that can be activated by the --inspect and related command line flags. This debugger service was vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution.</p>
<h1>'path' module regular expression denial of service (CVE-2018-7158)</h1>
<p>The 'path' module in the Node.js 4.x release line contains a potential regular expression denial of service (ReDoS) vector. The code in question was replaced in Node.js 6.x and later so this vulnerability only impacts all versions of Node.js 4.x.</p>
<h1>Spaces in HTTP Content-Length header values are ignored (CVE-2018-7159)</h1>
<p>The HTTP parser in all current versions of Node.js ignores spaces in the Content-Length header, allowing input such as Content-Length: 1 2 to be interpreted as having a value of 12. The HTTP specification does not allow for spaces in the Content-Length value and the Node.js HTTP parser has been brought into line on this particular difference.</p>
</blockquote>
</body>
</description>
<references>
<url>https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/</url>
<cvename>CVE-2018-7158</cvename>
<cvename>CVE-2018-7159</cvename>
<cvename>CVE-2018-7160</cvename>
</references>
<dates>
<discovery>2018-03-21</discovery>
<entry>2018-03-28</entry>
<modified>2018-03-28</modified>
</dates>
</vuln>
<vuln vid="1ce95bc7-3278-11e8-b527-00012e582166">
<topic>webkit2-gtk3 -- multiple vulnerabilities</topic>
<affects>
<package>
<name>webkit2-gtk3</name>
<range><ge>2.16.6</ge><lt>2.20.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The WebKit team reports many vulnerabilities.</p>
<p>Please reference the CVE/URL list for details.</p>
</body>
</description>
<references>
<url>https://webkitgtk.org/security/WSA-2017-0008.html</url>
<url>https://webkitgtk.org/security/WSA-2017-0009.html</url>
<url>https://webkitgtk.org/security/WSA-2017-0010.html</url>
<url>https://webkitgtk.org/security/WSA-2018-0001.html</url>
<url>https://webkitgtk.org/security/WSA-2018-0002.html</url>
<cvename>CVE-2017-7087</cvename>
<cvename>CVE-2017-7089</cvename>
<cvename>CVE-2017-7090</cvename>
<cvename>CVE-2017-7091</cvename>
<cvename>CVE-2017-7092</cvename>
<cvename>CVE-2017-7092</cvename>
<cvename>CVE-2017-7093</cvename>
<cvename>CVE-2017-7095</cvename>
<cvename>CVE-2017-7096</cvename>
<cvename>CVE-2017-7098</cvename>
<cvename>CVE-2017-7100</cvename>
<cvename>CVE-2017-7102</cvename>
<cvename>CVE-2017-7104</cvename>
<cvename>CVE-2017-7107</cvename>
<cvename>CVE-2017-7109</cvename>
<cvename>CVE-2017-7111</cvename>
<cvename>CVE-2017-7117</cvename>
<cvename>CVE-2017-7120</cvename>
<cvename>CVE-2017-13783</cvename>
<cvename>CVE-2017-13784</cvename>
<cvename>CVE-2017-13785</cvename>
<cvename>CVE-2017-13788</cvename>
<cvename>CVE-2017-13791</cvename>
<cvename>CVE-2017-13792</cvename>
<cvename>CVE-2017-13794</cvename>
<cvename>CVE-2017-13795</cvename>
<cvename>CVE-2017-13796</cvename>
<cvename>CVE-2017-13798</cvename>
<cvename>CVE-2017-13802</cvename>
<cvename>CVE-2017-13803</cvename>
<cvename>CVE-2017-7156</cvename>
<cvename>CVE-2017-7157</cvename>
<cvename>CVE-2017-13856</cvename>
<cvename>CVE-2017-13866</cvename>
<cvename>CVE-2017-13870</cvename>
<cvename>CVE-2017-5753</cvename>
<cvename>CVE-2017-5715</cvename>
<cvename>CVE-2018-4088</cvename>
<cvename>CVE-2018-4089</cvename>
<cvename>CVE-2018-4096</cvename>
<cvename>CVE-2017-7153</cvename>
<cvename>CVE-2017-7160</cvename>
<cvename>CVE-2017-7161</cvename>
<cvename>CVE-2017-7165</cvename>
<cvename>CVE-2017-13884</cvename>
<cvename>CVE-2017-13885</cvename>
</references>
<dates>
<discovery>2017-10-18</discovery>
<entry>2018-03-28</entry>
<modified>2018-03-28</modified>
</dates>
</vuln>
<vuln vid="3ae21918-31e3-11e8-927b-e8e0b747a45a">
<topic>chromium -- vulnerability</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>65.0.3325.181</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop_20.html">
<p>1 security fix in this release, including:</p>
<ul>
<li>[823553] Various fixes from internal audits, fuzzing and other initiatives</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop_20.html</url>
</references>
<dates>
<discovery>2018-03-20</discovery>
<entry>2018-03-27</entry>
</dates>
</vuln>
<vuln vid="b7cff5a9-31cc-11e8-8f07-b499baebfeaf">
<topic>OpenSSL -- multiple vulnerabilities</topic>
<affects>
<package>
<name>openssl</name>
<range><lt>1.0.2o,1</lt></range>
</package>
<package>
<name>openssl-devel</name>
<range><lt>1.1.0h</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The OpenSSL project reports:</p>
<blockquote cite="https://www.openssl.org/news/secadv/20180327.txt">
<ul><li>Constructed ASN.1 types with a recursive definition could
exceed the stack (CVE-2018-0739)<br/>
Constructed ASN.1 types with a recursive definition (such as can be
found in PKCS7) could eventually exceed the stack given malicious input
with excessive recursion. This could result in a Denial Of Service
attack. There are no such structures used within SSL/TLS that come from
untrusted sources so this is considered safe.</li>
<li>rsaz_1024_mul_avx2 overflow bug on x86_64 (CVE-2017-3738)<br/>
There is an overflow bug in the AVX2 Montgomery multiplication
procedure used in exponentiation with 1024-bit moduli. This only
affects processors that support the AVX2 but not ADX extensions
like Intel Haswell (4th generation).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://www.openssl.org/news/secadv/20180327.txt</url>
<cvename>CVE-2018-0739</cvename>
<cvename>CVE-2017-3738</cvename>
</references>
<dates>
<discovery>2018-03-27</discovery>
<entry>2018-03-27</entry>
</dates>
</vuln>
<vuln vid="dc0c201c-31da-11e8-ac53-d8cb8abf62dd">
<topic>Gitlab -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab</name>
<range><ge>10.5.0</ge><lt>10.5.6</lt></range>
<range><ge>10.4.0</ge><lt>10.4.6</lt></range>
<range><ge>8.3</ge><lt>10.3.9</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GitLab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/03/20/critical-security-release-gitlab-10-dot-5-dot-6-released/">
<h1>SSRF in services and web hooks</h1>
<p>There were multiple server-side request forgery issues in the Services feature.
An attacker could make requests to servers within the same network of the GitLab
instance. This could lead to information disclosure, authentication bypass, or
potentially code execution. This issue has been assigned
<a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8801">CVE-2018-8801</a>.</p>
<h1>Gitlab Auth0 integration issue</h1>
<p>There was an issue with the GitLab <code>omniauth-auth0</code> configuration
which resulted in the Auth0 integration signing in the wrong users.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-8801</cvename>
<url>https://about.gitlab.com/2018/03/20/critical-security-release-gitlab-10-dot-5-dot-6-released/</url>
</references>
<dates>
<discovery>2018-03-20</discovery>
<entry>2018-03-27</entry>
<modified>2018-04-07</modified>
</dates>
</vuln>
<vuln vid="23f59689-0152-42d3-9ade-1658d6380567">
<topic>mozilla -- use-after-free in compositor</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>59.0.2,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.0.4.36_3</lt></range>
</package>
<package>
<name>seamonkey</name>
<name>linux-seamonkey</name>
<range><lt>2.49.3</lt></range>
</package>
<package>
<name>firefox-esr</name>
<range><lt>52.7.3,1</lt></range>
</package>
<package>
<name>linux-firefox</name>
<range><lt>52.7.3,2</lt></range>
</package>
<package>
<name>libxul</name>
<range><lt>52.7.3</lt></range>
</package>
<package>
<name>linux-thunderbird</name>
<range><lt>52.7.1</lt></range>
</package>
<package>
<name>thunderbird</name>
<range><lt>52.7.0_1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-10/">
<h1>CVE-2018-5148: Use-after-free in compositor</h1>
<p>A use-after-free vulnerability can occur in the
compositor during certain graphics operations when a raw
pointer is used instead of a reference counted one. This
results in a potentially exploitable crash.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-5148</cvename>
<url>https://www.mozilla.org/security/advisories/mfsa2018-10/</url>
</references>
<dates>
<discovery>2018-03-26</discovery>
<entry>2018-03-27</entry>
<modified>2018-03-31</modified>
</dates>
</vuln>
<vuln vid="81946ace-6961-4488-a164-22d58ebc8d66">
<topic>rails-html-sanitizer -- possible XSS vulnerability</topic>
<affects>
<package>
<name>rubygem-rails-html-sanitizer</name>
<range><lt>1.0.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>OSS-Security list:</p>
<blockquote cite="http://www.openwall.com/lists/oss-security/2018/03/22/4">
<p>There is a possible XSS vulnerability in rails-html-sanitizer. The gem
allows non-whitelisted attributes to be present in sanitized output
when input with specially-crafted HTML fragments, and these attributes
can lead to an XSS attack on target applications.</p>
<p>This issue is similar to CVE-2018-8048 in Loofah.</p>
</blockquote>
</body>
</description>
<references>
<url>http://www.openwall.com/lists/oss-security/2018/03/22/4</url>
<cvename>CVE-2018-3741</cvename>
</references>
<dates>
<discovery>2018-03-22</discovery>
<entry>2018-03-24</entry>
</dates>
</vuln>
<vuln vid="f38187e7-2f6e-11e8-8f07-b499baebfeaf">
<topic>apache -- multiple vulnerabilities</topic>
<affects>
<package>
<name>apache24</name>
<range><lt>2.4.30</lt></range>
</package>
<package>
<name>apache22</name>
<range><lt>2.2.34_5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Apache httpd reports:</p>
<blockquote cite="https://www.apache.org/dist/httpd/CHANGES_2.4.33">
<p>Out of bound write in mod_authnz_ldap with AuthLDAPCharsetConfig
enabled (CVE-2017-15710)</p>
<p>mod_session: CGI-like applications that intend to read from
mod_session's 'SessionEnv ON' could be fooled into reading
user-supplied data instead. (CVE-2018-1283)</p>
<p>mod_cache_socache: Fix request headers parsing to avoid a possible
crash with specially crafted input data. (CVE-2018-1303)</p>
<p>core: Possible crash with excessively long HTTP request headers.
Impractical to exploit with a production build and production
LogLevel. (CVE-2018-1301)</p>
<p>core: Configure the regular expression engine to match '$' to the
end of the input string only, excluding matching the end of any
embedded newline characters. Behavior can be changed with new
directive 'RegexDefaultOptions'. (CVE-2017-15715)</p>
<p>mod_auth_digest: Fix generation of nonce values to prevent replay
attacks across servers using a common Digest domain. This change
may cause problems if used with round robin load balancers.
(CVE-2018-1312)</p>
<p>mod_http2: Potential crash w/ mod_http2. (CVE-2018-1302)</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.apache.org/dist/httpd/CHANGES_2.4.33</url>
<cvename>CVE-2017-15710</cvename>
<cvename>CVE-2018-1283</cvename>
<cvename>CVE-2018-1303</cvename>
<cvename>CVE-2018-1301</cvename>
<cvename>CVE-2017-15715</cvename>
<cvename>CVE-2018-1312</cvename>
<cvename>CVE-2018-1302</cvename>
</references>
<dates>
<discovery>2018-03-23</discovery>
<entry>2018-03-24</entry>
<modified>2018-03-27</modified>
</dates>
</vuln>
<vuln vid="d50a50a2-2f3e-11e8-86f8-00e04c1ea73d">
<topic>mybb -- multiple vulnerabilities</topic>
<affects>
<package>
<name>mybb</name>
<range><lt>1.8.15</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>mybb Team reports:</p>
<blockquote cite="https://blog.mybb.com/2018/03/15/mybb-1-8-15-released-security-maintenance-release/">
<p>Medium risk: Tasks Local File Inclusion</p>
<p>Medium risk: Forum Password Check Bypass</p>
<p>Low risk: Admin Permissions Group Title XSS</p>
<p>Low risk: Attachment types file extension XSS</p>
<p>Low risk: Moderator Tools XSS</p>
<p>Low risk: Security Questions XSS</p>
<p>Low risk: Settings Management XSS</p>
<p>Low risk: Templates Set Name XSS</p>
<p>Low risk: Usergroup Promotions XSS</p>
<p>Low risk: Warning Types XSS</p>
</blockquote>
</body>
</description>
<references>
<url>https://blog.mybb.com/2018/03/15/mybb-1-8-15-released-security-maintenance-release/</url>
</references>
<dates>
<discovery>2018-03-15</discovery>
<entry>2018-03-24</entry>
</dates>
</vuln>
<vuln vid="6d52bda1-2e54-11e8-a68f-485b3931c969">
<topic>SQLite -- Corrupt DB can cause a NULL pointer dereference</topic>
<affects>
<package>
<name>sqlite3</name>
<range><lt>3.22.0_1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>MITRE reports:</p>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2018-8740">
<p>SQLite databases whose schema is corrupted using a CREATE TABLE AS
statement could cause a NULL pointer dereference, related to build.c
and prepare.c.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-8740</cvename>
<url>http://openwall.com/lists/oss-security/2018/03/17/1</url>
</references>
<dates>
<discovery>2018-03-16</discovery>
<entry>2018-03-22</entry>
</dates>
</vuln>
<vuln vid="39a30e0a-0c34-431b-9dce-b87cab02412a">
<topic>Sanitize -- XSS vulnerability</topic>
<affects>
<package>
<name>rubygem-sanitize</name>
<range><lt>2.6.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Sanitize release:</p>
<blockquote cite="https://github.com/rgrove/sanitize/releases">
<p>Fixed an HTML injection vulnerability that could allow XSS.</p>
<p>When Sanitize <= 4.6.2 is used in combination with libxml2 >= 2.9.2,
a specially crafted HTML fragment can cause libxml2 to generate
improperly escaped output, allowing non-whitelisted attributes to be
used on whitelisted elements.</p>
<p>Sanitize now performs additional escaping on affected attributes to
prevent this.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/rgrove/sanitize/releases</url>
<url>https://github.com/rgrove/sanitize/issues/176</url>
<cvename>CVE-2018-3740</cvename>
</references>
<dates>
<discovery>2018-03-19</discovery>
<entry>2018-03-21</entry>
</dates>
</vuln>
<vuln vid="ba6d0c9b-f5f6-4b9b-a6de-3cce93c83220">
<topic>Loofah -- XSS vulnerability</topic>
<affects>
<package>
<name>rubygem-loofah</name>
<range><lt>2.2.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GitHub issue:</p>
<blockquote cite="https://github.com/flavorjones/loofah/issues/144">
<p>This issue has been created for public disclosure of an XSS / code
injection vulnerability that was responsibly reported by the Shopify
Application Security Team.</p>
<p>Loofah allows non-whitelisted attributes to be present in sanitized
output when input with specially-crafted HTML fragments.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/flavorjones/loofah/releases</url>
<url>https://github.com/flavorjones/loofah/issues/144</url>
<cvename>CVE-2018-8048</cvename>
</references>
<dates>
<discovery>2018-03-15</discovery>
<entry>2018-03-20</entry>
</dates>
</vuln>
<vuln vid="b3edc7d9-9af5-4daf-88f1-61f68f4308c2">
<topic>Jupyter Notebook -- vulnerability</topic>
<affects>
<package>
<name>py27-notebook</name>
<name>py34-notebook</name>
<name>py35-notebook</name>
<name>py36-notebook</name>
<range><lt>5.4.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>MITRE reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8768">
<p>In Jupyter Notebook before 5.4.1, a maliciously forged notebook file
can bypass sanitization to execute JavaScript in the notebook context.
Specifically, invalid HTML is 'fixed' by jQuery after sanitization,
making it dangerous.</p>
</blockquote>
</body>
</description>
<references>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8768</url>
<cvename>CVE-2018-8768</cvename>
</references>
<dates>
<discovery>2018-03-18</discovery>
<entry>2018-03-19</entry>
</dates>
</vuln>
<vuln vid="928d5c59-2a5a-11e8-a712-0025908740c2">
<topic>SquirrelMail -- post-authentication access privileges</topic>
<affects>
<package>
<name>squirrelmail</name>
<range><le>20170705</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Florian Grunow reports:</p>
<blockquote cite="https://insinuator.net/2018/03/squirrelmail-full-disclosure-troopers18/">
<p> An attacker able to exploit this vulnerability can extract files
of the server the application is running on. This may include
configuration files, log files and additionally all files that are
readable for all users on the system. This issue is
post-authentication. That means an attacker would need valid
credentials for the application to log in or needs to exploit an
additional vulnerability of which we are not aware of at this point
of time.</p>
<p>An attacker would also be able to delete files on the system, if
the user running the application has the rights to do so.</p>
<p>Does this issue affect me?</p>
<p>Likely yes, if you are using Squirrelmail. We checked the latest
development version, which is 1.5.2-svn and the latest version
available for download at this point of time, 1.4.22. Both contain
the vulnerable code.</p>
</blockquote>
</body>
</description>
<references>
<url>http://www.openwall.com/lists/oss-security/2018/03/17/2</url>
<url>https://nvd.nist.gov/vuln/detail/CVE-2018-8741</url>
<cvename>CVE-2018-8741</cvename>
</references>
<dates>
<discovery>2017-05-21</discovery>
<entry>2018-03-17</entry>
</dates>
</vuln>
<vuln vid="b3e04661-2a0a-11e8-9e63-3085a9a47796">
<topic>slurm-wlm -- SQL Injection attacks against SlurmDBD</topic>
<affects>
<package>
<name>slurm-wlm</name>
<range><lt>17.02.10</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>SchedMD reports:</p>
<blockquote cite="https://lists.schedmd.com/pipermail/slurm-announce/2018/000006.html">
<p>Several issues were discovered with incomplete sanitization of
user-provided text strings, which could potentially lead to SQL
injection attacks against SlurmDBD itself. Such exploits could lead to a
loss of accounting data, or escalation of user privileges on the cluster.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-7033</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2018-7033</url>
</references>
<dates>
<discovery>2018-03-15</discovery>
<entry>2018-03-17</entry>
</dates>
</vuln>
<vuln vid="64ee858e-e035-4bb4-9c77-2468963dddb8">
<topic>libvorbis -- multiple vulnerabilities</topic>
<affects>
<package>
<name>libvorbis</name>
<range><lt>1.3.6,3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>NVD reports:</p>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2017-14632">
<p>Xiph.Org libvorbis 1.3.5 allows Remote Code Execution
upon freeing uninitialized memory in the function
vorbis_analysis_headerout() in info.c when
vi->channels<=0, a similar issue to Mozilla bug
550184.</p>
</blockquote>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2017-14633">
<p>In Xiph.Org libvorbis 1.3.5, an out-of-bounds array read
vulnerability exists in the function mapping0_forward() in
mapping0.c, which may lead to DoS when operating on a
crafted audio file with vorbis_analysis().</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-14632</cvename>
<cvename>CVE-2017-14633</cvename>
</references>
<dates>
<discovery>2018-03-16</discovery>
<entry>2018-03-16</entry>
</dates>
</vuln>
<vuln vid="7943794f-707f-4e31-9fea-3bbf1ddcedc1">
<topic>mozilla -- multiple vulnerabilities</topic>
<affects>
<package>
<name>libvorbis</name>
<range><lt>1.3.6,3</lt></range>
</package>
<package>
<name>libtremor</name>
<range><lt>1.2.1.s20180316</lt></range>
</package>
<package>
<name>firefox</name>
<range><lt>59.0.1,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.0.4.36_3</lt></range>
</package>
<package>
<name>seamonkey</name>
<name>linux-seamonkey</name>
<range><lt>2.49.3</lt></range>
</package>
<package>
<name>firefox-esr</name>
<range><lt>52.7.2,1</lt></range>
</package>
<package>
<name>linux-firefox</name>
<range><lt>52.7.2,2</lt></range>
</package>
<package>
<name>libxul</name>
<range><lt>52.7.3</lt></range>
</package>
<package>
<name>thunderbird</name>
<name>linux-thunderbird</name>
<range><lt>52.7.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-08/">
<h1>CVE-2018-5146: Out of bounds memory write in libvorbis</h1>
<p>An out of bounds memory write while processing Vorbis
audio data was reported through the Pwn2Own contest.</p>
<h1>CVE-2018-5147: Out of bounds memory write in libtremor</h1>
<p>The libtremor library has the same flaw as
CVE-2018-5146. This library is used by Firefox in place of
libvorbis on Android and ARM platforms.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-5146</cvename>
<cvename>CVE-2018-5147</cvename>
<url>https://www.mozilla.org/security/advisories/mfsa2018-08/</url>
<url>https://www.mozilla.org/security/advisories/mfsa2018-09/</url>
</references>
<dates>
<discovery>2018-03-16</discovery>
<entry>2018-03-16</entry>
<modified>2018-03-31</modified>
</dates>
</vuln>
<vuln vid="2aa9967c-27e0-11e8-9ae1-080027ac955c">
<topic>e2fsprogs -- potential buffer overrun bugs in the blkid library and in the fsck program</topic>
<affects>
<package>
<name>e2fsprogs</name>
<range><lt>1.44.0</lt></range>
</package>
<package>
<name>e2fsprogs-libblkid</name>
<range><lt>1.44.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Theodore Y. Ts'o reports:</p>
<blockquote cite="http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.44.0">
<p>Fixed some potential buffer overrun bugs in the blkid library and in the fsck program.</p>
</blockquote>
</body>
</description>
<references>
<url>http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.44.0</url>
</references>
<dates>
<discovery>2018-03-07</discovery>
<entry>2018-03-14</entry>
</dates>
</vuln>
<vuln vid="74daa370-2797-11e8-95ec-a4badb2f4699">
<topic>FreeBSD -- Speculative Execution Vulnerabilities</topic>
<affects>
<package>
<name>FreeBSD-kernel</name>
<range><ge>11.1</ge><lt>11.1_8</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>A number of issues relating to speculative execution
were found last year and publicly announced January 3rd.
Two of these, known as Meltdown and Spectre V2, are addressed
here.</p>
<p>CVE-2017-5754 (Meltdown) - ------------------------</p>
<p>This issue relies on an affected CPU speculatively
executing instructions beyond a faulting instruction. When
this happens, changes to architectural state are not
committed, but observable changes may be left in micro-
architectural state (for example, cache). This may be used
to infer privileged data.</p>
<p>CVE-2017-5715 (Spectre V2) - --------------------------</p>
<p>Spectre V2 uses branch target injection to speculatively
execute kernel code at an address under the control of an
attacker.</p>
<h1>Impact:</h1>
<p>An attacker may be able to read secret data from the
kernel or from a process when executing untrusted code (for
example, in a web browser).</p>
</body>
</description>
<references>
<cvename>CVE-2017-5715</cvename>
<cvename>CVE-2017-5754</cvename>
<freebsdsa>SA-18:03.speculative_execution</freebsdsa>
</references>
<dates>
<discovery>2018-03-14</discovery>
<entry>2018-03-14</entry>
</dates>
</vuln>
<vuln vid="dca7ced0-2796-11e8-95ec-a4badb2f4699">
<topic>FreeBSD -- ipsec validation and use-after-free</topic>
<affects>
<package>
<name>FreeBSD-kernel</name>
<range><ge>11.1</ge><lt>11.1_7</lt></range>
<range><ge>10.4</ge><lt>10.4_7</lt></range>
<range><ge>10.3</ge><lt>10.3_28</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>Due to a lack of strict checking, an attacker from a
trusted host can send a specially constructed IP packet
that may lead to a system crash.</p>
<p>Additionally, a use-after-free vulnerability in the AH
handling code could cause unpredictable results.</p>
<h1>Impact:</h1>
<p>Access to out of bounds or freed mbuf data can lead to
a kernel panic or other unpredictable results.</p>
</body>
</description>
<references>
<cvename>CVE-2018-6916</cvename>
<freebsdsa>SA-18:01.ipsec</freebsdsa>
</references>
<dates>
<discovery>2018-03-07</discovery>
<entry>2018-03-14</entry>
</dates>
</vuln>
<vuln vid="313078e3-26e2-11e8-9920-6451062f0f7a">
<topic>Flash Player -- multiple vulnerabilities</topic>
<affects>
<package>
<name>linux-flashplayer</name>
<range><lt>29.0.0.113</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Adobe reports:</p>
<blockquote cite="https://helpx.adobe.com/security/products/flash-player/apsb18-05.html">
<ul>
<li>This update resolves a use-after-free vulnerability that
could lead to remote code execution (CVE-2018-4919).</li>
<li>This update resolves a type confusion vulnerability that
could lead to remote code execution (CVE-2018-4920).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-4919</cvename>
<cvename>CVE-2018-4920</cvename>
<url>https://helpx.adobe.com/security/products/flash-player/apsb18-05.html</url>
</references>
<dates>
<discovery>2018-03-13</discovery>
<entry>2018-03-13</entry>
</dates>
</vuln>
<vuln vid="c71cdc95-3c18-45b7-866a-af28b59aabb5">
<topic>mozilla -- multiple vulnerabilities</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>59.0_1,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.0.4.36_3</lt></range>
</package>
<package>
<name>seamonkey</name>
<name>linux-seamonkey</name>
<range><lt>2.49.3</lt></range>
</package>
<package>
<name>firefox-esr</name>
<range><lt>52.7.0,1</lt></range>
</package>
<package>
<name>linux-firefox</name>
<range><lt>52.7.0,2</lt></range>
</package>
<package>
<name>libxul</name>
<name>thunderbird</name>
<name>linux-thunderbird</name>
<range><lt>52.7.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-06/">
<p>CVE-2018-5127: Buffer overflow manipulating SVG animatedPathSegList</p>
<p>CVE-2018-5128: Use-after-free manipulating editor selection ranges</p>
<p>CVE-2018-5129: Out-of-bounds write with malformed IPC messages</p>
<p>CVE-2018-5130: Mismatched RTP payload type can trigger memory corruption</p>
<p>CVE-2018-5131: Fetch API improperly returns cached copies of no-store/no-cache resources</p>
<p>CVE-2018-5132: WebExtension Find API can search privileged pages</p>
<p>CVE-2018-5133: Value of the app.support.baseURL preference is not properly sanitized</p>
<p>CVE-2018-5134: WebExtensions may use view-source: URLs to bypass content restrictions</p>
<p>CVE-2018-5135: WebExtension browserAction can inject scripts into unintended contexts</p>
<p>CVE-2018-5136: Same-origin policy violation with data: URL shared workers</p>
<p>CVE-2018-5137: Script content can access legacy extension non-contentaccessible resources</p>
<p>CVE-2018-5138: Android Custom Tab address spoofing through long domain names</p>
<p>CVE-2018-5140: Moz-icon images accessible to web content through moz-icon: protocol</p>
<p>CVE-2018-5141: DOS attack through notifications Push API</p>
<p>CVE-2018-5142: Media Capture and Streams API permissions display incorrect origin with data: and blob: URLs</p>
<p>CVE-2018-5143: Self-XSS pasting javascript: URL with embedded tab into addressbar</p>
<p>CVE-2018-5126: Memory safety bugs fixed in Firefox 59</p>
<p>CVE-2018-5125: Memory safety bugs fixed in Firefox 59 and Firefox ESR 52.7</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-5125</cvename>
<cvename>CVE-2018-5126</cvename>
<cvename>CVE-2018-5127</cvename>
<cvename>CVE-2018-5128</cvename>
<cvename>CVE-2018-5129</cvename>
<cvename>CVE-2018-5130</cvename>
<cvename>CVE-2018-5131</cvename>
<cvename>CVE-2018-5132</cvename>
<cvename>CVE-2018-5133</cvename>
<cvename>CVE-2018-5134</cvename>
<cvename>CVE-2018-5135</cvename>
<cvename>CVE-2018-5136</cvename>
<cvename>CVE-2018-5137</cvename>
<cvename>CVE-2018-5138</cvename>
<cvename>CVE-2018-5140</cvename>
<cvename>CVE-2018-5141</cvename>
<cvename>CVE-2018-5142</cvename>
<cvename>CVE-2018-5143</cvename>
<url>https://www.mozilla.org/security/advisories/mfsa2018-06/</url>
<url>https://www.mozilla.org/security/advisories/mfsa2018-07/</url>
</references>
<dates>
<discovery>2018-03-13</discovery>
<entry>2018-03-13</entry>
<modified>2018-03-16</modified>
</dates>
</vuln>
<vuln vid="fb26f78a-26a9-11e8-a1c2-00505689d4ae">
<topic>samba -- multiple vulnerabilities</topic>
<affects>
<package>
<name>samba44</name>
<range><lt>4.4.17</lt></range>
</package>
<package>
<name>samba45</name>
<range><lt>4.5.16</lt></range>
</package>
<package>
<name>samba46</name>
<range><lt>4.6.14</lt></range>
</package>
<package>
<name>samba47</name>
<range><lt>4.7.6</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The samba project reports:</p>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-1050.html">
<p>Missing null pointer checks may crash the external
print server process.</p>
</blockquote>
<blockquote cite="https://www.samba.org/samba/security/CVE-2018-1057.html">
<p>On a Samba 4 AD DC any authenticated user can change
other user's passwords over LDAP, including the
passwords of administrative users and service accounts.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.samba.org/samba/security/CVE-2018-1050.html</url>
<cvename>CVE-2018-1050</cvename>
<url>https://www.samba.org/samba/security/CVE-2018-1057.html</url>
<cvename>CVE-2018-1057</cvename>
</references>
<dates>
<discovery>2018-01-03</discovery>
<entry>2018-03-13</entry>
</dates>
</vuln>
<vuln vid="c2f107e1-2493-11e8-b3e8-001cc0382b2f">
<topic>mbed TLS (PolarSSL) -- remote code execution</topic>
<affects>
<package>
<name>mbedtls</name>
<range><lt>2.7.0</lt></range>
</package>
<package>
<name>polarssl13</name>
<range><lt>1.3.22</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Simon Butcher reports:</p>
<blockquote cite="https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2018-01">
<ul>
<li>When the truncated HMAC extension is enabled and CBC is used,
sending a malicious application packet can be used to selectively
corrupt 6 bytes on the peer's heap, potentially leading to a
crash or remote code execution. This can be triggered remotely
from either side in both TLS and DTLS.</li>
<li>When RSASSA-PSS signature verification is enabled, sending a
maliciously constructed certificate chain can be used to cause a
buffer overflow on the peer's stack, potentially leading to crash
or remote code execution. This can be triggered remotely from
either side in both TLS and DTLS.</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2018-01</url>
<cvename>CVE-2018-0487</cvename>
<cvename>CVE-2018-0488</cvename>
</references>
<dates>
<discovery>2018-02-05</discovery>
<entry>2018-03-10</entry>
</dates>
</vuln>
<vuln vid="555af074-22b9-11e8-9799-54ee754af08e">
<topic>chromium -- vulnerability</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>65.0.3325.146</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html">
<p>45 security fixes in this release:</p>
<ul>
<li>[758848] High CVE-2017-11215: Use after free in Flash. Reported by JieZeng of Tencent Zhanlu Lab on 2017-08-25</li>
<li>[758863] High CVE-2017-11225: Use after free in Flash. Reported by JieZeng of Tencent Zhanlu Lab on 2017-08-25</li>
<li>[780919] High CVE-2018-6060: Use after free in Blink. Reported by Omair on 2017-11-02</li>
<li>[794091] High CVE-2018-6061: Race condition in V8. Reported by Guang Gong of Alpha Team, Qihoo 360 on 2017-12-12</li>
<li>[780104] High CVE-2018-6062: Heap buffer overflow in Skia. Reported by Anonymous on 2017-10-31</li>
<li>[789959] High CVE-2018-6057: Incorrect permissions on shared memory. Reported by Gal Beniamini of Google Project Zero on 2017-11-30</li>
<li>[792900] High CVE-2018-6063: Incorrect permissions on shared memory. Reported by Gal Beniamini of Google Project Zero on 2017-12-07</li>
<li>[798644] High CVE-2018-6064: Type confusion in V8. Reported by lokihardt of Google Project Zero on 2018-01-03</li>
<li>[808192] High CVE-2018-6065: Integer overflow in V8. Reported by Mark Brand of Google Project Zero on 2018-02-01</li>
<li>[799477] Medium CVE-2018-6066: Same Origin Bypass via canvas. Reported by Masato Kinugawa on 2018-01-05</li>
<li>[779428] Medium CVE-2018-6067: Buffer overflow in Skia. Reported by Ned Williamson on 2017-10-30</li>
<li>[779428] Medium CVE-2018-6067: Buffer overflow in Skia. Reported by Ned Williamson on 2017-10-30</li>
<li>[799918] Medium CVE-2018-6069: Stack buffer overflow in Skia. Reported by Wanglu and Yangkang(@dnpushme) of Qihoo360 Qex Team on 2018-01-08</li>
<li>[668645] Medium CVE-2018-6070: CSP bypass through extensions. Reported by Rob Wu on 2016-11-25</li>
<li>[777318] Medium CVE-2018-6071: Heap bufffer overflow in Skia. Reported by Anonymous on 2017-10-23</li>
<li>[791048] Medium CVE-2018-6072: Integer overflow in PDFium. Reported by Atte Kettunen of OUSPG on 2017-12-01</li>
<li>[804118] Medium CVE-2018-6073: Heap bufffer overflow in WebGL. Reported by Omair on 2018-01-20</li>
<li>[809759] Medium CVE-2018-6074: Mark-of-the-Web bypass. Reported by Abdulrahman Alqabandi (@qab) on 2018-02-06</li>
<li>[608669] Medium CVE-2018-6075: Overly permissive cross origin downloads. Reported by Inti De Ceukelaire (intigriti.com) on 2016-05-03</li>
<li>[758523] Medium CVE-2018-6076: Incorrect handling of URL fragment identifiers in Blink. Reported by Mateusz Krzeszowiec on 2017-08-24</li>
<li>[778506] Medium CVE-2018-6077: Timing attack using SVG filters. Reported by Khalil Zhani on 2017-10-26</li>
<li>[793628] Medium CVE-2018-6078: URL Spoof in OmniBox. Reported by Khalil Zhani on 2017-12-10</li>
<li>[788448] Medium CVE-2018-6079: Information disclosure via texture data in WebGL. Reported by Ivars Atteka on 2017-11-24</li>
<li>[792028] Medium CVE-2018-6080: Information disclosure in IPC call. Reported by Gal Beniamini of Google Project Zero on 2017-12-05</li>
<li>[797525] Low CVE-2018-6081: XSS in interstitials. Reported by Rob Wu on 2017-12-24</li>
<li>[767354] Low CVE-2018-6082: Circumvention of port blocking. Reported by WenXu Wu of Tencent's Xuanwu Lab on 2017-09-21</li>
<li>[771709] Low CVE-2018-6083: Incorrect processing of AppManifests. Reported by Jun Kokatsu (@shhnjk) on 2017-10-04</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-11215</cvename>
<cvename>CVE-2017-11225</cvename>
<cvename>CVE-2018-6060</cvename>
<cvename>CVE-2018-6061</cvename>
<cvename>CVE-2018-6060</cvename>
<cvename>CVE-2018-6061</cvename>
<cvename>CVE-2018-6062</cvename>
<cvename>CVE-2018-6057</cvename>
<cvename>CVE-2018-6063</cvename>
<cvename>CVE-2018-6064</cvename>
<cvename>CVE-2018-6065</cvename>
<cvename>CVE-2018-6066</cvename>
<cvename>CVE-2018-6067</cvename>
<cvename>CVE-2018-6069</cvename>
<cvename>CVE-2018-6070</cvename>
<cvename>CVE-2018-6071</cvename>
<cvename>CVE-2018-6072</cvename>
<cvename>CVE-2018-6073</cvename>
<cvename>CVE-2018-6074</cvename>
<cvename>CVE-2018-6075</cvename>
<cvename>CVE-2018-6076</cvename>
<cvename>CVE-2018-6077</cvename>
<cvename>CVE-2018-6078</cvename>
<cvename>CVE-2018-6079</cvename>
<cvename>CVE-2018-6080</cvename>
<cvename>CVE-2018-6081</cvename>
<cvename>CVE-2018-6082</cvename>
<cvename>CVE-2018-6083</cvename>
<url>https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html</url>
</references>
<dates>
<discovery>2016-05-03</discovery>
<entry>2018-03-08</entry>
</dates>
</vuln>
<vuln vid="c5ab620f-4576-4ad5-b51f-93e4fec9cd0e">
<topic>wireshark -- multiple security issues</topic>
<affects>
<package>
<name>wireshark</name>
<range><ge>2.2.0</ge><lt>2.2.13</lt></range>
<range><ge>2.4.0</ge><lt>2.4.5</lt></range>
</package>
<package>
<name>wireshark-lite</name>
<range><ge>2.2.0</ge><lt>2.2.13</lt></range>
<range><ge>2.4.0</ge><lt>2.4.5</lt></range>
</package>
<package>
<name>wireshark-qt5</name>
<range><ge>2.2.0</ge><lt>2.2.13</lt></range>
<range><ge>2.4.0</ge><lt>2.4.5</lt></range>
</package>
<package>
<name>tshark</name>
<range><ge>2.2.0</ge><lt>2.2.13</lt></range>
<range><ge>2.4.0</ge><lt>2.4.5</lt></range>
</package>
<package>
<name>tshark-lite</name>
<range><ge>2.2.0</ge><lt>2.2.13</lt></range>
<range><ge>2.4.0</ge><lt>2.4.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>wireshark developers reports:</p>
<blockquote cite="https://www.wireshark.org/security/">
<p>wnpa-sec-2018-05. IEEE 802.11 dissector crash. (CVE-2018-7335)</p>
<p>wnpa-sec-2018-06. Large or infinite loops in multiple dissectors. (CVE-2018-7321 through CVE-2018-7333)</p>
<p>wnpa-sec-2018-07. UMTS MAC dissector crash. (CVE-2018-7334)</p>
<p>wnpa-sec-2018-08. DOCSIS dissector crash. (CVE-2018-7337)</p>
<p>wnpa-sec-2018-09. FCP dissector crash. (CVE-2018-7336)</p>
<p>wnpa-sec-2018-10. SIGCOMP dissector crash. (CVE-2018-7320)</p>
<p>wnpa-sec-2018-11. Pcapng file parser crash.</p>
<p>wnpa-sec-2018-12. IPMI dissector crash.</p>
<p>wnpa-sec-2018-13. SIGCOMP dissector crash.</p>
<p>wnpa-sec-2018-14. NBAP dissector crash.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.wireshark.org/security/</url>
<url>https://www.wireshark.org/security/wnpa-sec-2018-05.html</url>
<url>https://www.wireshark.org/security/wnpa-sec-2018-06.html</url>
<url>https://www.wireshark.org/security/wnpa-sec-2018-07.html</url>
<url>https://www.wireshark.org/security/wnpa-sec-2018-08.html</url>
<url>https://www.wireshark.org/security/wnpa-sec-2018-09.html</url>
<url>https://www.wireshark.org/security/wnpa-sec-2018-10.html</url>
<url>https://www.wireshark.org/security/wnpa-sec-2018-11.html</url>
<url>https://www.wireshark.org/security/wnpa-sec-2018-12.html</url>
<url>https://www.wireshark.org/security/wnpa-sec-2018-13.html</url>
<url>https://www.wireshark.org/security/wnpa-sec-2018-14.html</url>
<cvename>CVE-2018-7320</cvename>
<cvename>CVE-2018-7321</cvename>
<cvename>CVE-2018-7322</cvename>
<cvename>CVE-2018-7323</cvename>
<cvename>CVE-2018-7324</cvename>
<cvename>CVE-2018-7325</cvename>
<cvename>CVE-2018-7326</cvename>
<cvename>CVE-2018-7327</cvename>
<cvename>CVE-2018-7328</cvename>
<cvename>CVE-2018-7329</cvename>
<cvename>CVE-2018-7330</cvename>
<cvename>CVE-2018-7331</cvename>
<cvename>CVE-2018-7332</cvename>
<cvename>CVE-2018-7333</cvename>
<cvename>CVE-2018-7334</cvename>
<cvename>CVE-2018-7335</cvename>
<cvename>CVE-2018-7336</cvename>
<cvename>CVE-2018-7337</cvename>
<cvename>CVE-2018-7417</cvename>
</references>
<dates>
<discovery>2018-02-23</discovery>
<entry>2018-03-04</entry>
</dates>
</vuln>
<vuln vid="2040c7f5-1e3a-11e8-8ae9-0050569f0b83">
<topic>isc-dhcp -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>isc-dhcp44-server</name>
<range><lt>4.4.1</lt></range>
</package>
<package>
<name>isc-dhcp44-client</name>
<range><lt>4.4.1</lt></range>
</package>
<package>
<name>isc-dhcp43-server</name>
<range><le>4.3.6</le></range>
</package>
<package>
<name>isc-dhcp43-client</name>
<range><le>4.3.6</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>ISC reports:</p>
<blockquote cite="https://kb.isc.org/article/AA-01565">
<p>Failure to properly bounds check a buffer used for processing
DHCP options allows a malicious server (or an entity
masquerading as a server) to cause a buffer overflow (and
resulting crash) in dhclient by sending a response containing a
specially constructed options section.</p>
</blockquote>
<blockquote cite="https://kb.isc.org/article/AA-01567">
<p>A malicious client which is allowed to send very large amounts
of traffic (billions of packets) to a DHCP server can eventually
overflow a 32-bit reference counter, potentially causing dhcpd
to crash.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-5732</cvename>
<cvename>CVE-2018-5733</cvename>
<url>https://kb.isc.org/article/AA-01565</url>
<url>https://kb.isc.org/article/AA-01567</url>
</references>
<dates>
<discovery>2018-02-21</discovery>
<entry>2018-03-02</entry>
</dates>
</vuln>
<vuln vid="30704aba-1da4-11e8-b6aa-4ccc6adda413">
<topic>libsndfile -- out-of-bounds reads</topic>
<affects>
<package>
<name>libsndfile</name>
<name>linux-c6-libsndfile</name>
<name>linux-c7-libsndfile</name>
<range><lt>1.0.28_2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Xin-Jiang on Github reports:</p>
<blockquote cite="https://github.com/erikd/libsndfile/issues/317">
<p>CVE-2017-14245 (Medium): An out of bounds read in the function
d2alaw_array() in alaw.c of libsndfile 1.0.28 may lead to a remote
DoS attack or information disclosure, related to mishandling of
the NAN and INFINITY floating-point values.</p>
<p>CVE-2017-14246 (Medium): An out of bounds read in the function
d2ulaw_array() in ulaw.c of libsndfile 1.0.28 may lead to a remote
DoS attack or information disclosure, related to mishandling of the
NAN and INFINITY floating-point values.</p>
</blockquote>
<p>my123px on Github reports:</p>
<blockquote cite="https://github.com/erikd/libsndfile/issues/344">
<p>CVE-2017-17456 (Medium): The function d2alaw_array() in alaw.c of
libsndfile 1.0.29pre1 may lead to a remote DoS attack (SEGV on unknown
address 0x000000000000), a different vulnerability than CVE-2017-14245.</p>
<p>CVE-2017-17457 (Medium): The function d2ulaw_array() in ulaw.c of
libsndfile 1.0.29pre1 may lead to a remote DoS attack (SEGV on unknown
address 0x000000000000), a different vulnerability than CVE-2017-14246.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-14245</cvename>
<cvename>CVE-2017-14246</cvename>
<url>https://github.com/erikd/libsndfile/issues/317</url>
<cvename>CVE-2017-17456</cvename>
<cvename>CVE-2017-17457</cvename>
<url>https://github.com/erikd/libsndfile/issues/344</url>
</references>
<dates>
<discovery>2017-09-11</discovery>
<entry>2018-03-01</entry>
</dates>
</vuln>
<vuln vid="2b386075-1d9c-11e8-b6aa-4ccc6adda413">
<topic>libsndfile -- multiple vulnerabilities</topic>
<affects>
<package>
<name>libsndfile</name>
<name>linux-c6-libsndfile</name>
<name>linux-c7-libsndfile</name>
<range><lt>1.0.28_2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Agostino Sarubbo, Gentoo reports:</p>
<blockquote cite="https://blogs.gentoo.org/ago/2017/04/29/libsndfile-global-buffer-overflow-in-flac_buffer_copy-flac-c/">
<p>CVE-2017-8361 (Medium): The flac_buffer_copy function in flac.c in
libsndfile 1.0.28 allows remote attackers to cause a denial of service
(buffer overflow and application crash) or possibly have unspecified
other impact via a crafted audio file.</p>
</blockquote>
<blockquote cite="https://blogs.gentoo.org/ago/2017/04/29/libsndfile-invalid-memory-read-in-flac_buffer_copy-flac-c/">
<p>CVE-2017-8362 (Medium): The flac_buffer_copy function in flac.c in
libsndfile 1.0.28 allows remote attackers to cause a denial of service
(invalid read and application crash) via a crafted audio file.</p>
</blockquote>
<blockquote cite="https://blogs.gentoo.org/ago/2017/04/29/libsndfile-heap-based-buffer-overflow-in-flac_buffer_copy-flac-c/">
<p>CVE-2017-8363 (Medium): The flac_buffer_copy function in flac.c in
libsndfile 1.0.28 allows remote attackers to cause a denial of service
(heap-based buffer over-read and application crash) via a crafted audio
file.</p>
</blockquote>
<blockquote cite="https://blogs.gentoo.org/ago/2017/04/29/libsndfile-global-buffer-overflow-in-i2les_array-pcm-c/">
<p>CVE-2017-8365 (Medium): The i2les_array function in pcm.c in libsndfile
1.0.28 allows remote attackers to cause a denial of service (buffer
over-read and application crash) via a crafted audio file.</p>
</blockquote>
<p>manxorist on Github reports:</p>
<blockquote cite="https://github.com/erikd/libsndfile/issues/292">
<p>CVE-2017-12562 (High): Heap-based Buffer Overflow in the
psf_binheader_writef function in common.c in libsndfile through
1.0.28 allows remote attackers to cause a denial of service
(application crash) or possibly have unspecified other impact.</p>
</blockquote>
<p>Xin-Jiang on Github reports:</p>
<blockquote cite="https://github.com/erikd/libsndfile/issues/318">
<p>CVE-2017-14634 (Medium): In libsndfile 1.0.28, a divide-by-zero
error exists in the function double64_init() in double64.c, which
may lead to DoS when playing a crafted audio file.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-8361</cvename>
<url>https://blogs.gentoo.org/ago/2017/04/29/libsndfile-global-buffer-overflow-in-flac_buffer_copy-flac-c/</url>
<url>https://github.com/erikd/libsndfile/issues/232</url>
<url>https://github.com/erikd/libsndfile/commit/fd0484aba8e51d16af1e3a880f9b8b857b385eb3</url>
<cvename>CVE-2017-8362</cvename>
<url>https://blogs.gentoo.org/ago/2017/04/29/libsndfile-invalid-memory-read-in-flac_buffer_copy-flac-c/</url>
<url>https://github.com/erikd/libsndfile/issues/231</url>
<url>https://github.com/erikd/libsndfile/commit/ef1dbb2df1c0e741486646de40bd638a9c4cd808</url>
<cvename>CVE-2017-8363</cvename>
<url>https://blogs.gentoo.org/ago/2017/04/29/libsndfile-heap-based-buffer-overflow-in-flac_buffer_copy-flac-c/</url>
<url>https://github.com/erikd/libsndfile/issues/233</url>
<url>https://github.com/erikd/libsndfile/commit/fd0484aba8e51d16af1e3a880f9b8b857b385eb3</url>
<url>https://github.com/erikd/libsndfile/commit/cd7da8dbf6ee4310d21d9e44b385d6797160d9e8</url>
<cvename>CVE-2017-8365</cvename>
<url>https://blogs.gentoo.org/ago/2017/04/29/libsndfile-global-buffer-overflow-in-i2les_array-pcm-c/</url>
<url>https://github.com/erikd/libsndfile/issues/230</url>
<url>https://github.com/erikd/libsndfile/commit/fd0484aba8e51d16af1e3a880f9b8b857b385eb3</url>
<cvename>CVE-2017-12562</cvename>
<url>https://github.com/erikd/libsndfile/issues/292/</url>
<url>https://github.com/erikd/libsndfile/commit/cf7a8182c2642c50f1cf90dddea9ce96a8bad2e8</url>
<cvename>CVE-2017-14634</cvename>
<url>https://github.com/erikd/libsndfile/issues/318</url>
<url>https://github.com/erikd/libsndfile/commit/85c877d5072866aadbe8ed0c3e0590fbb5e16788</url>
</references>
<dates>
<discovery>2017-04-12</discovery>
<entry>2018-03-01</entry>
</dates>
</vuln>
<vuln vid="e3eeda2e-1d67-11e8-a2ec-6cc21735f730">
<topic>PostgreSQL vulnerabilities</topic>
<affects>
<package>
<name>postgresql93-server</name>
<range><ge>9.3.0</ge><lt>9.3.22</lt></range>
</package>
<package>
<name>postgresql94-server</name>
<range><ge>9.4.0</ge><lt>9.4.17</lt></range>
</package>
<package>
<name>postgresql95-server</name>
<range><ge>9.5.0</ge><lt>9.5.12</lt></range>
</package>
<package>
<name>postgresql96-server</name>
<range><ge>9.6.0</ge><lt>9.6.8</lt></range>
</package>
<package>
<name>postgresql10-server</name>
<range><ge>10.0</ge><lt>10.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The PostgreSQL project reports:</p>
<blockquote cite="https://www.postgresql.org/about/news/1834/">
<ul>
<li>CVE-2018-1058: Uncontrolled search path element in pg_dump and other client applications</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path</url>
<cvename>CVE-2018-1058</cvename>
</references>
<dates>
<discovery>2018-03-01</discovery>
<entry>2018-03-01</entry>
</dates>
</vuln>
<vuln vid="6a449a37-1570-11e8-8e00-000c294a5758">
<topic>strongswan - Insufficient input validation in RSASSA-PSS signature parser</topic>
<affects>
<package>
<name>strongswan</name>
<range><eq>5.6.1</eq></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Strongswan Release Notes reports:</p>
<blockquote cite="https://github.com/strongswan/strongswan/blob/master/NEWS">
<p>Fixed a DoS vulnerability in the parser for PKCS#1 RSASSA-PSS signatures that
was caused by insufficient input validation. One of the configurable
parameters in algorithm identifier structures for RSASSA-PSS signatures is the
mask generation function (MGF). Only MGF1 is currently specified for this
purpose. However, this in turn takes itself a parameter that specifies the
underlying hash function. strongSwan's parser did not correctly handle the
case of this parameter being absent, causing an undefined data read.
his vulnerability has been registered as CVE-2018-6459.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-6459</cvename>
<url>https://github.com/strongswan/strongswan/commit/40da179f28b768ffcf6ff7e2f68675eb44806668</url>
</references>
<dates>
<discovery>2018-01-31</discovery>
<entry>2018-02-19</entry>
</dates>
</vuln>
<vuln vid="004debf9-1d16-11e8-b6aa-4ccc6adda413">
<topic>libsndfile -- out-of-bounds read memory access</topic>
<affects>
<package>
<name>libsndfile</name>
<name>linux-c6-libsndfile</name>
<name>linux-c7-libsndfile</name>
<range><lt>1.0.28_2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Laurent Delosieres, Secunia Research at Flexera Software reports:</p>
<blockquote cite="https://secuniaresearch.flexerasoftware.com/secunia_research/2017-13/">
<p>Secunia Research has discovered a vulnerability in libsndfile, which can be
exploited by malicious people to disclose potentially sensitive information.
The vulnerability is caused due to an error in the "aiff_read_chanmap()" function
(src/aiff.c), which can be exploited to cause an out-of-bounds read memory access
via a specially crafted AIFF file. The vulnerability is confirmed in version 1.0.28.
Other versions may also be affected.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-6892</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2017-6892</url>
<url>https://secuniaresearch.flexerasoftware.com/secunia_research/2017-13/</url>
<url>https://github.com/erikd/libsndfile/commit/f833c53cb596e9e1792949f762e0b33661822748</url>
</references>
<dates>
<discovery>2017-05-23</discovery>
<entry>2018-03-01</entry>
</dates>
</vuln>
<vuln vid="af485ef4-1c58-11e8-8477-d05099c0ae8c">
<topic>ntp -- multiple vulnerabilities</topic>
<affects>
<package>
<name>FreeBSD</name>
<range><ge>11.1</ge><lt>11.1_7</lt></range>
<range><ge>10.4</ge><lt>10.4_6</lt></range>
<range><ge>10.3</ge><lt>10.3_27</lt></range>
</package>
<package>
<name>ntp</name>
<range><lt>4.2.8p11</lt></range>
</package>
<package>
<name>ntp-devel</name>
<range><gt>0</gt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Network Time Foundation reports:</p>
<blockquote cite="http://support.ntp.org/bin/view/Main/SecurityNotice#February_2018_ntp_4_2_8p11_NTP_S">
<p>The NTP Project at Network Time Foundation is releasing ntp-4.2.8p11.</p>
<p>This release addresses five security issues in ntpd:</p>
<ul>
<li>LOW/MEDIUM: Sec 3012 / CVE-2016-1549 / VU#961909: Sybil
vulnerability: ephemeral association attack</li>
<li>INFO/MEDIUM: Sec 3412 / CVE-2018-7182 / VU#961909:
ctl_getitem(): buffer read overrun leads to undefined
behavior and information leak</li>
<li>LOW: Sec 3415 / CVE-2018-7170 / VU#961909: Multiple
authenticated ephemeral associations</li>
<li>LOW: Sec 3453 / CVE-2018-7184 / VU#961909: Interleaved
symmetric mode cannot recover from bad state</li>
<li>LOW/MEDIUM: Sec 3454 / CVE-2018-7185 / VU#961909:
Unauthenticated packet can reset authenticated interleaved
association</li>
</ul>
<p>one security issue in ntpq:</p>
<ul>
<li>MEDIUM: Sec 3414 / CVE-2018-7183 / VU#961909:
ntpq:decodearr() can write beyond its buffer limit</li>
</ul>
<p>and provides over 33 bugfixes and 32 other improvements.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2016-1549</cvename>
<cvename>CVE-2018-7182</cvename>
<cvename>CVE-2018-7170</cvename>
<cvename>CVE-2018-7184</cvename>
<cvename>CVE-2018-7185</cvename>
<cvename>CVE-2018-7183</cvename>
<freebsdsa>SA-18:02.ntp</freebsdsa>
<url>http://support.ntp.org/bin/view/Main/SecurityNotice#February_2018_ntp_4_2_8p11_NTP_S</url>
</references>
<dates>
<discovery>2018-02-27</discovery>
<entry>2018-02-28</entry>
<modified>2018-03-14</modified>
</dates>
</vuln>
<vuln vid="abfc932e-1ba8-11e8-a944-54ee754af08e">
<topic>chromium -- vulnerability</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>64.0.3282.167</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2018/02/stable-channel-update-for-desktop_13.html">
<p>1 security fix in this release:</p>
<ul>
<li>[806388] High CVE-2018-6056: Incorrect derived class instantiation in V8. Reported by lokihardt of Google Project Zero on 2018-01-26</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-6056</cvename>
<url>https://chromereleases.googleblog.com/2018/02/stable-channel-update-for-desktop_13.html</url>
</references>
<dates>
<discovery>2018-01-26</discovery>
<entry>2018-02-27</entry>
</dates>
</vuln>
<vuln vid="8e986b2b-1baa-11e8-a944-54ee754af08e">
<topic>chromium -- multiple vulnerabilities</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>64.0.3282.119</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html">
<p>Several security fixes in this release, including:</p>
<ul>
<li>[780450] High CVE-2018-6031: Use after free in PDFium. Reported by Anonymous on 2017-11-01</li>
<li>[787103] High CVE-2018-6032: Same origin bypass in Shared Worker. Reported by Jun Kokatsu (@shhnjk) on 2017-11-20</li>
<li>[793620] High CVE-2018-6033: Race when opening downloaded files. Reported by Juho Nurminen on 2017-12-09</li>
<li>[784183] Medium CVE-2018-6034: Integer overflow in Blink. Reported by Tobias Klein (www.trapkit.de) on 2017-11-12</li>
<li>[797500] Medium CVE-2018-6035: Insufficient isolation of devtools from extensions. Reported by Rob Wu on 2017-12-23</li>
<li>[797500] Medium CVE-2018-6035: Insufficient isolation of devtools from extensions. Reported by Rob Wu on 2017-12-23</li>
<li>[753645] Medium CVE-2018-6037: Insufficient user gesture requirements in autofill. Reported by Paul Stone of Context Information Security on
2017-08-09</li>
<li>[774174] Medium CVE-2018-6038: Heap buffer overflow in WebGL. Reported by cloudfuzzer on 2017-10-12</li>
<li>[775527] Medium CVE-2018-6039: XSS in DevTools. Reported by Juho Nurminen on 2017-10-17</li>
<li>[778658] Medium CVE-2018-6040: Content security policy bypass. Reported by WenXu Wu of Tencent's Xuanwu Lab on 2017-10-26</li>
<li>[760342] Medium CVE-2018-6041: URL spoof in Navigation. Reported by Luan Herrera on 2017-08-29</li>
<li>[773930] Medium CVE-2018-6042: URL spoof in OmniBox. Reported by Khalil Zhani on 2017-10-12</li>
<li>[785809] Medium CVE-2018-6043: Insufficient escaping with external URL handlers. Reported by 0x09AL on 2017-11-16</li>
<li>[797497] Medium CVE-2018-6045: Insufficient isolation of devtools from extensions. Reported by Rob Wu on 2017-12-23</li>
<li>[798163] Medium CVE-2018-6046: Insufficient isolation of devtools from extensions. Reported by Rob Wu on 2017-12-31</li>
<li>[799847] Medium CVE-2018-6047: Cross origin URL leak in WebGL. Reported by Masato Kinugawa on 2018-01-08</li>
<li>[763194] Low CVE-2018-6048: Referrer policy bypass in Blink. Reported by Jun Kokatsu (@shhnjk) on 2017-09-08</li>
<li>[771848] Low CVE-2017-15420: URL spoofing in Omnibox. Reported by Drew Springall (@_aaspring_) on 2017-10-05</li>
<li>[774438] Low CVE-2018-6049: UI spoof in Permissions. Reported by WenXu Wu of Tencent's Xuanwu Lab on 2017-10-13</li>
<li>[774842] Low CVE-2018-6050: URL spoof in OmniBox. Reported by Jonathan Kew on 2017-10-15</li>
<li>[441275] Low CVE-2018-6051: Referrer leak in XSS Auditor. Reported by Antonio Sanso (@asanso) on 2014-12-11</li>
<li>[615608] Low CVE-2018-6052: Incomplete no-referrer policy implementation. Reported by Tanner Emek on 2016-05-28</li>
<li>[758169] Low CVE-2018-6053: Leak of page thumbnails in New Tab Page. Reported by Asset Kabdenov on 2017-08-23</li>
<li>[797511] Low CVE-2018-6054: Use after free in WebUI. Reported by Rob Wu on 2017-12-24</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-6031</cvename>
<cvename>CVE-2018-6032</cvename>
<cvename>CVE-2018-6033</cvename>
<cvename>CVE-2018-6034</cvename>
<cvename>CVE-2018-6035</cvename>
<cvename>CVE-2018-6036</cvename>
<cvename>CVE-2018-6037</cvename>
<cvename>CVE-2018-6038</cvename>
<cvename>CVE-2018-6039</cvename>
<cvename>CVE-2018-6040</cvename>
<cvename>CVE-2018-6041</cvename>
<cvename>CVE-2018-6042</cvename>
<cvename>CVE-2018-6043</cvename>
<cvename>CVE-2018-6045</cvename>
<cvename>CVE-2018-6046</cvename>
<cvename>CVE-2018-6047</cvename>
<cvename>CVE-2018-6048</cvename>
<cvename>CVE-2017-15420</cvename>
<cvename>CVE-2018-6049</cvename>
<cvename>CVE-2018-6050</cvename>
<cvename>CVE-2018-6051</cvename>
<cvename>CVE-2018-6052</cvename>
<cvename>CVE-2018-6053</cvename>
<cvename>CVE-2018-6054</cvename>
<url>https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html</url>
</references>
<dates>
<discovery>2017-08-09</discovery>
<entry>2018-02-27</entry>
</dates>
</vuln>
<vuln vid="55c4233e-1844-11e8-a712-0025908740c2">
<topic>tomcat -- Security constraints ignored or applied too late</topic>
<affects>
<package>
<name>tomcat</name>
<range><ge>7.0.0</ge><le>7.0.84</le></range>
<range><ge>8.0.0</ge><le>8.0.49</le></range>
<range><ge>8.5.0</ge><le>8.5.27</le></range>
<range><ge>9.0.0</ge><le>9.0.4</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Apache Software Foundation reports:</p>
<blockquote cite="https://lists.apache.org/thread.html/d3354bb0a4eda4acc0a66f3eb24a213fdb75d12c7d16060b23e65781@%3Cannounce.tomcat.apache.org%3E">
<p>Security constraints defined by annotations of Servlets were only
applied once a Servlet had been loaded. Because security constraints
defined in this way apply to the URL pattern and any URLs below that
point, it was possible - depending on the order Servlets were loaded -
for some security constraints not to be applied. This could have exposed
resources to users who were not authorised to access them.</p>
</blockquote>
<blockquote cite="https://lists.apache.org/thread.html/b1d7e2425d6fd2cebed40d318f9365b44546077e10949b01b1f8a0fb@%3Cannounce.tomcat.apache.org%3E">
<p>The URL pattern of "" (the empty string) which exactly maps to the
context root was not correctly handled when used as part of a security
constraint definition. This caused the constraint to be ignored. It was,
therefore, possible for unauthorised users to gain access to web
application resources that should have been protected. Only security
constraints with a URL pattern of the empty string were affected.</p>
</blockquote>
</body>
</description>
<references>
<url>http://tomcat.apache.org/security-9.html</url>
<url>http://tomcat.apache.org/security-8.html</url>
<url>http://tomcat.apache.org/security-7.html</url>
<cvename>CVE-2018-1304</cvename>
<cvename>CVE-2018-1305</cvename>
</references>
<dates>
<discovery>2018-02-23</discovery>
<entry>2018-02-23</entry>
</dates>
</vuln>
<vuln vid="22438240-1bd0-11e8-a2ec-6cc21735f730">
<topic>shibboleth-sp -- vulnerable to forged user attribute data</topic>
<affects>
<package>
<name>xmltooling</name>
<range><lt>1.6.4</lt></range>
</package>
<package>
<name>xerces-c3</name>
<range><lt>3.1.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Shibboleth consortium reports:</p>
<blockquote cite="https://shibboleth.net/community/advisories/secadv_20180227.txt">
<p>
Shibboleth SP software vulnerable to additional data forgery flaws
</p>
<p>
The XML processing performed by the Service Provider software has
been found to be vulnerable to new flaws similar in nature to the
one addressed in an advisory last month.
</p>
<p>
These bugs involve the use of other XML constructs rather than
entity references, and therefore required additional mitigation once
discovered. As with the previous issue, this flaw allows for
changes to an XML document that do not break a digital signature but
can alter the user data passed through to applications behind the SP
and result in impersonation attacks and exposure of protected
information.
</p>
<p>
As before, the use of XML Encryption is a significant mitigation,
but we have not dismissed the possibility that attacks on the
Response "envelope" may be possible, in both the original and this
new case. No actual attacks of this nature are known, so deployers
should prioritize patching systems that expect to handle unencrypted
SAML assertions.
</p>
<p>
An updated version of XMLTooling-C (V1.6.4) is available that
protects against these new attacks, and should help prevent similar
vulnerabilities in the future.
</p>
<p>
Unlike the previous case, these bugs are NOT prevented by any
existing Xerces-C parser version on any platform and cannot be
addressed by any means other than the updated XMLTooling-C library.
</p>
<p>
The Service Provider software relies on a generic XML parser to
process SAML responses and there are limitations in older versions
of the parser that make it impossible to fully disable Document Type
Definition (DTD) processing.
</p>
<p>
Through addition/manipulation of a DTD, it's possible to make
changes to an XML document that do not break a digital signature but
are mishandled by the SP and its libraries. These manipulations can
alter the user data passed through to applications behind the SP and
result in impersonation attacks and exposure of protected
information.
</p>
<p>
While newer versions of the xerces-c3 parser are configured by the
SP into disallowing the use of a DTD via an environment variable,
this feature is not present in the xerces-c3 parser before version
3.1.4, so an additional fix is being provided now that an actual DTD
exploit has been identified. Xerces-c3-3.1.4 was committed to the
ports tree already on 2016-07-26.
</p>
</blockquote>
</body>
</description>
<references>
<url>https://shibboleth.net/community/advisories/secadv_20180227.txt</url>
<cvename>CVE-2018-0489</cvename>
</references>
<dates>
<discovery>2018-02-27</discovery>
<entry>2018-02-27</entry>
</dates>
</vuln>
<vuln vid="57580fcc-1a61-11e8-97e0-00e04c1ea73d">
<topic>drupal -- Drupal Core - Multiple Vulnerabilities</topic>
<affects>
<package>
<name>drupal7</name>
<range><lt>7.56</lt></range>
</package>
<package>
<name>drupal8</name>
<range><lt>8.4.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Drupal Security Team reports:</p>
<blockquote cite="https://www.drupal.org/SA-CORE-2018-001">
<p>CVE-2017-6926: Comment reply form allows access to restricted content</p>
<p>CVE-2017-6927: JavaScript cross-site scripting prevention is incomplete</p>
<p>CVE-2017-6928: Private file access bypass - Moderately Critical</p>
<p>CVE-2017-6929: jQuery vulnerability with untrusted domains - Moderately Critical</p>
<p>CVE-2017-6930: Language fallback can be incorrect on multilingual sites with node access restrictions</p>
<p>CVE-2017-6931: Settings Tray access bypass</p>
<p>CVE-2017-6932: External link injection on 404 pages when linking to the current page</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-6926</cvename>
<cvename>CVE-2017-6927</cvename>
<cvename>CVE-2017-6928</cvename>
<cvename>CVE-2017-6929</cvename>
<cvename>CVE-2017-6930</cvename>
<cvename>CVE-2017-6931</cvename>
<cvename>CVE-2017-6932</cvename>
</references>
<dates>
<discovery>2018-02-21</discovery>
<entry>2018-02-25</entry>
</dates>
</vuln>
<vuln vid="d9fe59ea-1940-11e8-9eb8-5404a68ad561">
<topic>cvs -- Remote code execution via ssh command injection</topic>
<affects>
<package>
<name>cvs</name>
<range><lt>1.20120905_5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Hank Leininger reports:</p>
<blockquote cite="http://lists.nongnu.org/archive/html/bug-cvs/2017-08/msg00000.html">
<p>Bugs in Git, Subversion, and Mercurial were just announced and patched
which allowed arbitrary local command execution if a malicious name was
used for the remote server, such as starting with - to pass options to
the ssh client:
git clone ssh://-oProxyCommand=some-command...
CVS has a similar problem with the -d option:</p>
<p>Tested vanilla CVS 1.12.13, and Gentoo CVS 1.12.12-r11.</p>
</blockquote>
</body>
</description>
<references>
<url>http://lists.nongnu.org/archive/html/bug-cvs/2017-08/msg00000.html</url>
<url>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871810#10</url>
<cvename>CVE-2017-12836</cvename>
<freebsdpr>ports/226088</freebsdpr>
</references>
<dates>
<discovery>2017-08-10</discovery>
<entry>2018-02-24</entry>
</dates>
</vuln>
<vuln vid="289269f1-0def-11e8-99b0-d017c2987f9a">
<topic>LibreOffice -- Remote arbitrary file disclosure vulnerability via WEBSERVICE formula</topic>
<affects>
<package>
<name>libreoffice</name>
<range><lt>5.4.5</lt></range>
<range><ge>6.0.0</ge><lt>6.0.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>LibreOffice reports:</p>
<blockquote cite="https://www.libreoffice.org/about-us/security/advisories/cve-2018-1055/">
<p>LibreOffice Calc supports a WEBSERVICE function to obtain data by URL.
Vulnerable versions of LibreOffice allow WEBSERVICE to take a local file
URL (e.g file://) which can be used to inject local files into the
spreadsheet without warning the user. Subsequent formulas can operate on
that inserted data and construct a remote URL whose path leaks the local
data to a remote attacker.</p>
<p>In later versions of LibreOffice without this flaw, WEBSERVICE has now
been limited to accessing http and https URLs along with bringing
WEBSERVICE URLs under LibreOffice Calc's link management infrastructure.</p>
<p><strong>Note:</strong> This vulnerability has been identified upstream
as CVE-2018-1055, but NVD/Mitre are advising it's a reservation
duplicate of CVE-2018-6871 which should be used instead.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.libreoffice.org/about-us/security/advisories/cve-2018-1055/</url>
<url>https://github.com/jollheef/libreoffice-remote-arbitrary-file-disclosure</url>
<cvename>CVE-2018-6871</cvename>
<freebsdpr>ports/225797</freebsdpr>
</references>
<dates>
<discovery>2018-02-09</discovery>
<entry>2018-02-23</entry>
</dates>
</vuln>
<vuln vid="d5b6d151-1887-11e8-94f7-9c5c8e75236a">
<topic>squid -- Vulnerable to Denial of Service attack</topic>
<affects>
<package>
<name>squid</name>
<range><lt>3.5.27_3</lt></range>
</package>
<package>
<name>squid-devel</name>
<range><lt>4.0.23</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Louis Dion-Marcil reports:</p>
<blockquote cite="http://www.squid-cache.org/Advisories/SQUID-2018_1.txt">
<p>Due to incorrect pointer handling Squid is vulnerable to denial
of service attack when processing ESI responses.</p>
<p>This problem allows a remote server delivering certain ESI
response syntax to trigger a denial of service for all clients
accessing the Squid service.</p>
<p>Due to unrelated changes Squid-3.5 has become vulnerable to some
regular ESI server responses also triggering this issue.</p>
<p>This problem is limited to the Squid custom ESI parser.
Squid built to use libxml2 or libexpat XML parsers do not have
this problem.</p>
</blockquote>
<blockquote cite="http://www.squid-cache.org/Advisories/SQUID-2018_2.txt">
<p>Due to incorrect pointer handling Squid is vulnerable to denial
of service attack when processing ESI responses or downloading
intermediate CA certificates.</p>
<p>This problem allows a remote client delivering certain HTTP
requests in conjunction with certain trusted server responses to
trigger a denial of service for all clients accessing the Squid
service.</p>
</blockquote>
</body>
</description>
<references>
<url>http://www.squid-cache.org/Advisories/SQUID-2018_1.txt</url>
<url>http://www.squid-cache.org/Advisories/SQUID-2018_2.txt</url>
<cvename>CVE-2018-1000024</cvename>
<cvename>CVE-2018-1000027</cvename>
<url>https://www.debian.org/security/2018/dsa-4122</url>
<freebsdpr>ports/226138</freebsdpr>
</references>
<dates>
<discovery>2017-12-13</discovery>
<entry>2018-02-23</entry>
</dates>
</vuln>
<vuln vid="933654ce-17b8-11e8-90b8-001999f8d30b">
<topic>asterisk -- multiple vulnerabilities</topic>
<affects>
<package>
<name>asterisk13</name>
<range><lt>13.19.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Asterisk project reports:</p>
<blockquote cite="http://www.asterisk.org/downloads/security-advisories">
<p>AST-2018-004 - When processing a SUBSCRIBE request the
res_pjsip_pubsub module stores the accepted formats present
in the Accept headers of the request. This code did not
limit the number of headers it processed despite having
a fixed limit of 32. If more than 32 Accept headers were
present the code would write outside of its memory and
cause a crash.</p>
<p>AST-2018-005 - A crash occurs when a number of
authenticated INVITE messages are sent over TCP or TLS
and then the connection is suddenly closed. This issue
leads to a segmentation fault.</p>
</blockquote>
</body>
</description>
<references>
<url>https://downloads.asterisk.org/pub/security/AST-2018-004.html</url>
<cvename>CVE-2018-7284</cvename>
<url>https://downloads.asterisk.org/pub/security/AST-2018-005.html</url>
<cvename>CVE-2018-7286</cvename>
</references>
<dates>
<discovery>2018-02-21</discovery>
<entry>2018-02-22</entry>
<modified>2018-06-12</modified>
</dates>
</vuln>
<vuln vid="f9f5c5a2-17b5-11e8-90b8-001999f8d30b">
<topic>asterisk and pjsip -- multiple vulnerabilities</topic>
<affects>
<package>
<name>asterisk13</name>
<range><lt>13.19.2</lt></range>
</package>
<package>
<name>pjsip</name>
<range><lt>2.7.2</lt></range>
</package>
<package>
<name>pjsip-extsrtp</name>
<range><lt>2.7.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Asterisk project reports:</p>
<blockquote cite="https://www.asterisk.org/downloads/security-advisories">
<p>AST-2018-002 - By crafting an SDP message with an
invalid media format description Asterisk crashes when
using the pjsip channel driver because pjproject's sdp
parsing algorithm fails to catch the invalid media format
description.</p>
<p>AST-2018-003 - By crafting an SDP message body with
an invalid fmtp attribute Asterisk crashes when using the
pjsip channel driver because pjproject's fmtp retrieval
function fails to check if fmtp value is empty (set empty
if previously parsed as invalid).</p>
</blockquote>
</body>
</description>
<references>
<url>https://downloads.asterisk.org/pub/security/AST-2018-002.html</url>
<url>https://downloads.asterisk.org/pub/security/AST-2018-003.html</url>
</references>
<dates>
<discovery>2018-02-21</discovery>
<entry>2018-02-22</entry>
</dates>
</vuln>
<vuln vid="261ca31c-179f-11e8-b8b9-6805ca0b3d42">
<topic>phpMyAdmin -- self XSS in central columns feature</topic>
<affects>
<package>
<name>phpMyAdmin</name>
<range><ge>4.7.0</ge><lt>4.7.8</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The phpMyAdmin team reports:</p>
<blockquote cite="https://www.phpmyadmin.net/security/PMASA-2018-1/">
<h3>Summary</h3>
<p>Self XSS in central columns feature</p>
<h3>Description</h3>
<p>A self-cross site scripting (XSS) vulnerability has been
reported relating to the central columns feature.</p>
<h3>Severity</h3>
<p>We consider this vulnerability to be of moderate severity.</p>
<h3>Mitigation factor</h3>
<p>A valid token must be used in the attack</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.phpmyadmin.net/security/PMASA-2018-1/</url>
<cvename>CVE-2018-7260</cvename>
</references>
<dates>
<discovery>2018-02-21</discovery>
<entry>2018-02-22</entry>
</dates>
</vuln>
<vuln vid="86291013-16e6-11e8-ae9f-d43d7e971a1b">
<topic>GitLab -- multiple vulnerabilities</topic>
<affects>
<package>
<name>gitlab</name>
<range><ge>6.1.0</ge><le>10.2.7</le></range>
<range><ge>10.3.0</ge><le>10.3.6</le></range>
<range><ge>10.4.0</ge><le>10.4.2</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GitLab reports:</p>
<blockquote cite="https://about.gitlab.com/2018/02/07/gitlab-security-10-4-3-plus-10-3-7-plus-10-2-8-blog/">
<h1>SnippetFinder information disclosure</h1>
<p>The GitLab SnippetFinder component contained an information disclosure
which allowed access to snippets restricted to Only team members or
configured as disabled. The issue is now resolved in the latest version.</p>
<h1>LDAP API authorization issue</h1>
<p>An LDAP API endpoint contained an authorization vulnerability which
unintentionally disclosed bulk LDAP groups data. This issue is now fixed in
the latest release.</p>
<h1>Persistent XSS mermaid markdown</h1>
<p>The mermaid markdown feature contained a persistent XSS issue that is now
resolved in the latest release.</p>
<h1>Insecure direct object reference Todo API</h1>
<p>The Todo API was vulnerable to an insecure direct object reference issue
which resulted in an information disclosure of confidential data.</p>
<h1>GitHub import access control issue</h1>
<p>An improper access control weakness issue was discovered in the GitHub
import feature. The issue allowed an attacker to create projects under other
accounts which they shouldn't have access to. The issue is now resolved in
the latest version.</p>
<h1>Protected variables information disclosure</h1>
<p>The CI jobs protected tag feature contained a vulnerability which
resulted in an information disclosure of protected variables. The issue is
now resolved in the latest release.</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/02/07/gitlab-security-10-4-3-plus-10-3-7-plus-10-2-8-blog/</url>
</references>
<dates>
<discovery>2018-02-07</discovery>
<entry>2018-02-21</entry>
</dates>
</vuln>
<vuln vid="7afc5e56-156d-11e8-95f2-005056925db4">
<topic>irssi -- multiple vulnerabilities</topic>
<affects>
<package>
<name>irssi</name>
<range><lt>1.1.1,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Irssi reports:</p>
<blockquote cite="https://irssi.org/security/irssi_sa_2018_02.txt">
<p>Use after free when server is disconnected during netsplits.
Found by Joseph Bisch.</p>
<p>Use after free when SASL messages are received in unexpected order.
Found by Joseph Bisch.</p>
<p>Null pointer dereference when an “empty” nick has been observed by
Irssi. Found by Joseph Bisch.</p>
<p>When the number of windows exceed the available space, Irssi would
crash due to Null pointer dereference. Found by Joseph Bisch.</p>
<p>Certain nick names could result in out of bounds access when printing
theme strings. Found by Oss-Fuzz.</p>
</blockquote>
</body>
</description>
<references>
<url>https://irssi.org/security/irssi_sa_2018_02.txt</url>
<cvename>CVE-2018-7054</cvename>
<cvename>CVE-2018-7053</cvename>
<cvename>CVE-2018-7052</cvename>
<cvename>CVE-2018-7051</cvename>
<cvename>CVE-2018-7050</cvename>
<freebsdpr>ports/226001</freebsdpr>
</references>
<dates>
<discovery>2018-02-15</discovery>
<entry>2018-02-19</entry>
<modified>2018-02-22</modified>
</dates>
</vuln>
<vuln vid="a183acb5-1414-11e8-9542-002590acae31">
<topic>p5-Mojolicious -- cookie-handling vulnerability</topic>
<affects>
<package>
<name>p5-Mojolicious</name>
<range><lt>7.66</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Upstream commit:</p>
<blockquote cite="https://github.com/kraih/mojo/commit/c16a56a9d6575ddc53d15e76d58f0ebcb0eeb149">
<p>Vulnerabilities existed in cookie handling.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/kraih/mojo/issues/1185</url>
</references>
<dates>
<discovery>2018-01-31</discovery>
<entry>2018-02-17</entry>
</dates>
</vuln>
<vuln vid="22283b8c-13c5-11e8-a861-20cf30e32f6d">
<topic>Bugzilla security issues</topic>
<affects>
<package>
<name>bugzilla44</name>
<range><lt>4.4.13</lt></range>
</package>
<package>
<name>bugzilla50</name>
<range><lt>5.0.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Bugzilla Security Advisory</p>
<blockquote cite="https://www.bugzilla.org/security/4.4.12/">
<p>A CSRF vulnerability in report.cgi would allow a third-party site
to extract confidential information from a bug the victim had access to.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-5123</cvename>
<url>https://bugzilla.mozilla.org/show_bug.cgi?id=1433400</url>
</references>
<dates>
<discovery>2018-02-16</discovery>
<entry>2018-02-16</entry>
</dates>
</vuln>
<vuln vid="044cff62-ed8b-4e72-b102-18a7d58a669f">
<topic>bro -- integer overflow allows remote DOS</topic>
<affects>
<package>
<name>bro</name>
<range><lt>2.5.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Philippe Antoine of Catena cyber:</p>
<blockquote cite="http://blog.bro.org/2018/02/bro-253-released-security-update.html">
<p>This is a security release that fixes an integer overflow in code generated by binpac. This issue can be used by remote attackers to crash Bro (i.e. a DoS attack). There also is a possibility this can be exploited in other ways. (CVE pending.)</p>
</blockquote>
</body>
</description>
<references>
<url>http://blog.bro.org/2018/02/bro-253-released-security-update.html</url>
</references>
<dates>
<discovery>2018-02-14</discovery>
<entry>2018-02-16</entry>
</dates>
</vuln>
<vuln vid="ad2eeab6-ca68-4f06-9325-1937b237df60">
<topic>consul -- vulnerability in embedded DNS library</topic>
<affects>
<package>
<name>consul</name>
<range><lt>1.0.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Consul developers report:</p>
<blockquote cite="https://github.com/hashicorp/consul/issues/3859">
<p>A flaw was found in the embedded DNS library used in consul which
may allow a denial of service attack. Consul was updated to include
the fixed version.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/hashicorp/consul/issues/3859</url>
<url>https://github.com/hashicorp/consul/blob/master/CHANGELOG.md#105-february-7-2018</url>
<url>https://github.com/miekg/dns/pull/631</url>
<url>https://github.com/miekg/dns/issues/627</url>
<cvename>CVE-2017-15133</cvename>
</references>
<dates>
<discovery>2018-01-17</discovery>
<entry>2018-02-16</entry>
</dates>
</vuln>
<vuln vid="746d04dc-507e-4450-911f-4c41e48bb07a">
<topic>bro -- out of bounds write allows remote DOS</topic>
<affects>
<package>
<name>bro</name>
<range><lt>2.5.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Frank Meier:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000458">
<p>Bro before Bro v2.5.2 is vulnerable to an out of bounds write in the ContentLine analyzer allowing remote attackers to cause a denial of service (crash) and possibly other exploitation.</p>
</blockquote>
</body>
</description>
<references>
<url>http://blog.bro.org/2017/10/bro-252-242-release-security-update.html</url>
</references>
<dates>
<discovery>2017-10-16</discovery>
<entry>2018-02-16</entry>
</dates>
</vuln>
<vuln vid="e15a22ce-f16f-446b-9ca7-6859350c2e75">
<topic>quagga -- several security issues</topic>
<affects>
<package>
<name>quagga</name>
<range><lt>1.2.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Quagga reports:</p>
<blockquote cite="https://www.quagga.net/security/Quagga-2018-0543.txt">
<p>The Quagga BGP daemon, bgpd, does not properly bounds
check the data sent with a NOTIFY to a peer, if an attribute
length is invalid. Arbitrary data from the bgpd process
may be sent over the network to a peer and/or it may crash.</p>
</blockquote>
<blockquote cite="https://www.quagga.net/security/Quagga-2018-1114.txt">
<p>The Quagga BGP daemon, bgpd, can double-free memory
when processing certain forms of UPDATE message, containing
cluster-list and/or unknown attributes.</p>
</blockquote>
<blockquote cite="https://www.quagga.net/security/Quagga-2018-1550.txt">
<p>The Quagga BGP daemon, bgpd, can overrun internal BGP
code-to-string conversion tables used for debug by 1
pointer value, based on input.</p>
</blockquote>
<blockquote cite="https://www.quagga.net/security/Quagga-2018-1975.txt">
<p>The Quagga BGP daemon, bgpd, can enter an infinite
loop if sent an invalid OPEN message by a configured peer.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.quagga.net/security/Quagga-2018-0543.txt</url>
<url>https://www.quagga.net/security/Quagga-2018-1114.txt</url>
<url>https://www.quagga.net/security/Quagga-2018-1550.txt</url>
<url>https://www.quagga.net/security/Quagga-2018-1975.txt</url>
<cvename>CVE-2018-5378</cvename>
<cvename>CVE-2018-5379</cvename>
<cvename>CVE-2018-5380</cvename>
<cvename>CVE-2018-5381</cvename>
</references>
<dates>
<discovery>2018-01-31</discovery>
<entry>2018-02-15</entry>
</dates>
</vuln>
<vuln vid="6f0b0cbf-1274-11e8-8b5b-4ccc6adda413">
<topic>libraw -- multiple DoS vulnerabilities</topic>
<affects>
<package>
<name>libraw</name>
<range><lt>0.18.7</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Secunia Research reports:</p>
<blockquote cite="https://www.securityfocus.com/archive/1/541732">
<p>CVE-2018-5800: An off-by-one error within the "LibRaw::kodak_ycbcr_load_raw()"
function (internal/dcraw_common.cpp) can be exploited to cause a heap-based
buffer overflow and subsequently cause a crash.</p>
<p>CVE-2017-5801: An error within the "LibRaw::unpack()" function
(src/libraw_cxx.cpp) can be exploited to trigger a NULL pointer dereference.</p>
<p>CVE-2017-5802: An error within the "kodak_radc_load_raw()" function
(internal/dcraw_common.cpp) related to the "buf" variable can be exploited
to cause an out-of-bounds read memory access and subsequently cause a crash.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.securityfocus.com/archive/1/541732</url>
<cvename>CVE-2018-5800</cvename>
<cvename>CVE-2018-5801</cvename>
<cvename>CVE-2018-5802</cvename>
</references>
<dates>
<discovery>2018-01-16</discovery>
<entry>2018-02-15</entry>
</dates>
</vuln>
<vuln vid="c60804f1-126f-11e8-8b5b-4ccc6adda413">
<topic>libraw -- multiple DoS vulnerabilities</topic>
<affects>
<package>
<name>libraw</name>
<range><lt>0.18.6</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Secunia Research reports:</p>
<blockquote cite="https://www.securityfocus.com/archive/1/541583">
<p>CVE-2017-16909: An error related to the "LibRaw::panasonic_load_raw()"
function (dcraw_common.cpp) can be exploited to cause a heap-based buffer
overflow and subsequently cause a crash via a specially crafted TIFF image.</p>
<p>CVE-2017-16910: An error within the "LibRaw::xtrans_interpolate()" function
(internal/dcraw_common.cpp) can be exploited to cause an invalid read
memory access.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.securityfocus.com/archive/1/541583</url>
<cvename>CVE-2017-16909</cvename>
<cvename>CVE-2017-16910</cvename>
</references>
<dates>
<discovery>2017-12-04</discovery>
<entry>2018-02-15</entry>
</dates>
</vuln>
<vuln vid="1a75c84a-11c8-11e8-83e7-485b3931c969">
<topic>bitmessage -- remote code execution vulnerability</topic>
<affects>
<package>
<name>bitmessage</name>
<range><le>0.6.2</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Bitmessage developers report:</p>
<blockquote cite="https://github.com/Bitmessage/PyBitmessage/releases/tag/v0.6.3">
<p>A remote code execution vulnerability has been spotted in use
against some users running PyBitmessage v0.6.2. The cause was
identified and a fix has been added and released as 0.6.3.2. (Will be
updated if/when CVE will be available.)</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/Bitmessage/PyBitmessage/releases/tag/v0.6.3</url>
<url>https://bitmessage.org/wiki/Main_Page</url>
</references>
<dates>
<discovery>2018-02-13</discovery>
<entry>2018-02-14</entry>
</dates>
</vuln>
<vuln vid="5d374fbb-bae3-45db-afc0-795684ac7353">
<topic>jenkins -- Path traversal vulnerability allows access to files outside plugin resources</topic>
<affects>
<package>
<name>jenkins</name>
<range><le>2.106</le></range>
</package>
<package>
<name>jenkins-lts</name>
<range><le>2.89.3</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Jenkins developers report:</p>
<blockquote cite="https://jenkins.io/security/advisory/2018-02-14/">
<p>Jenkins did not properly prevent specifying relative paths that
escape a base directory for URLs accessing plugin resource files. This
allowed users with Overall/Read permission to download files from the
Jenkins master they should not have access to.</p>
</blockquote>
</body>
</description>
<references>
<url>https://jenkins.io/security/advisory/2018-02-14/</url>
<url>https://jenkins.io/blog/2018/02/14/security-updates/</url>
<cvename>CVE-2018-6356</cvename>
</references>
<dates>
<discovery>2018-02-14</discovery>
<entry>2018-02-14</entry>
</dates>
</vuln>
<vuln vid="279f682c-0e9e-11e8-83e7-485b3931c969">
<topic>bchunk -- access violation near NULL on destination operand and crash</topic>
<affects>
<package>
<name>bchunk</name>
<range><ge>1.2.0</ge><le>1.2.1</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mitre reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15955">
<p>bchunk 1.2.0 and 1.2.1 is vulnerable to an "Access violation near
NULL on destination operand" and crash when processing a malformed CUE
(.cue) file.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-15955</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2017-15955</url>
</references>
<dates>
<discovery>2017-10-28</discovery>
<entry>2018-02-13</entry>
</dates>
</vuln>
<vuln vid="8ba2819c-0e9d-11e8-83e7-485b3931c969">
<topic>bchunk -- heap-based buffer overflow (with invalid free) and crash</topic>
<affects>
<package>
<name>bchunk</name>
<range><ge>1.2.0</ge><le>1.2.1</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mitre reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15954">
<p>bchunk 1.2.0 and 1.2.1 is vulnerable to a heap-based buffer
overflow (with a resultant invalid free) and crash when processing a
malformed CUE (.cue) file.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-15954</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2017-15954</url>
</references>
<dates>
<discovery>2017-10-28</discovery>
<entry>2018-02-13</entry>
</dates>
</vuln>
<vuln vid="1ec1c59b-0e98-11e8-83e7-485b3931c969">
<topic>bchunk -- heap-based buffer overflow and crash</topic>
<affects>
<package>
<name>bchunk</name>
<range><ge>1.2.0</ge><le>1.2.1</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mitre reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15953">
<p>bchunk 1.2.0 and 1.2.1 vulnerable to a heap-based buffer overflow
and crash when processing a malformed CUE (.cue) file.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-15953</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2017-15953</url>
</references>
<dates>
<discovery>2017-10-28</discovery>
<entry>2018-02-13</entry>
</dates>
</vuln>
<vuln vid="a8f25565-109e-11e8-8d41-97657151f8c2">
<topic>uwsgi -- a stack-based buffer overflow</topic>
<affects>
<package>
<name>uwsgi</name>
<range><lt>2.0.16</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Uwsgi developers report:</p>
<blockquote cite="http://lists.unbit.it/pipermail/uwsgi/2018-February/008835.html">
<p>It was discovered that the uwsgi_expand_path function in utils.c in
Unbit uWSGI, an application container server, has a stack-based buffer
overflow via a large directory length that can cause a
denial-of-service (application crash) or stack corruption.</p>
</blockquote>
</body>
</description>
<references>
<url>http://lists.unbit.it/pipermail/uwsgi/2018-February/008835.html</url>
<url>https://lists.debian.org/debian-lts-announce/2018/02/msg00010.html</url>
<cvename>CVE-2018-6758</cvename>
</references>
<dates>
<discovery>2018-02-06</discovery>
<entry>2018-02-13</entry>
</dates>
</vuln>
<vuln vid="0fe70bcd-2ce3-46c9-a64b-4a7da097db07">
<topic>python -- possible integer overflow vulnerability</topic>
<affects>
<package>
<name>python34</name>
<range><lt>3.4.8</lt></range>
</package>
<package>
<name>python35</name>
<range><lt>3.5.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Python issue:</p>
<blockquote cite="https://bugs.python.org/issue30657">
<p>There is a possible integer overflow in PyString_DecodeEscape
function of the file stringobject.c, which can be abused to gain
a heap overflow, possibly leading to arbitrary code execution.</p>
</blockquote>
</body>
</description>
<references>
<url>https://bugs.python.org/issue30657</url>
<url>https://docs.python.org/3.4/whatsnew/changelog.html</url>
<url>https://docs.python.org/3.5/whatsnew/changelog.html</url>
<cvename>CVE-2017-1000158</cvename>
</references>
<dates>
<discovery>2017-06-03</discovery>
<entry>2018-02-11</entry>
</dates>
</vuln>
<vuln vid="aa743ee4-0f16-11e8-8fd2-10bf48e1088e">
<topic>electrum -- JSONRPC vulnerability</topic>
<affects>
<package>
<name>electrum-py36</name>
<range><ge>2.6</ge><lt>3.0.5</lt></range>
</package>
<package>
<name>electrum2</name>
<range><ge>2.6</ge><lt>3.0.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>MITRE reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6353">
<p>JSONRPC vulnerability</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-6353</cvename>
<url>https://github.com/spesmilo/electrum-docs/blob/master/cve.rst</url>
<url>https://bitcointalk.org/index.php?topic=2702103.0</url>
</references>
<dates>
<discovery>2018-01-27</discovery>
<entry>2018-02-11</entry>
</dates>
</vuln>
<vuln vid="e4dd787e-0ea9-11e8-95f2-005056925db4">
<topic>libtorrent -- remote DoS</topic>
<affects>
<package>
<name>libtorrent</name>
<range><lt>0.13.6_5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>X-cela reports:</p>
<blockquote cite="https://github.com/rakshasa/libtorrent/pull/99">
<p>Calls into build_benocde that use %zu could crash on 64 bit
machines due to the size change of size_t. Someone can force
READ_ENC_IA to fail allowing an internal_error to be thrown
and bring down the client.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/rakshasa/libtorrent/pull/99</url>
<freebsdpr>ports/224664</freebsdpr>
</references>
<dates>
<discovery>2015-12-01</discovery>
<entry>2018-02-10</entry>
</dates>
</vuln>
<vuln vid="316b3c3e-0e98-11e8-8d41-97657151f8c2">
<topic>exim -- a buffer overflow vulnerability, remote code execution</topic>
<affects>
<package>
<name>exim</name>
<range><lt>4.90.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Exim developers report:</p>
<blockquote cite="https://exim.org/static/doc/security/CVE-2018-6789.txt">
<p>There is a buffer overflow in base64d(), if some pre-conditions are met.
Using a handcrafted message, remote code execution seems to be possible.</p>
</blockquote>
</body>
</description>
<references>
<url>https://exim.org/static/doc/security/CVE-2018-6789.txt</url>
</references>
<dates>
<discovery>2018-02-05</discovery>
<entry>2018-02-10</entry>
</dates>
</vuln>
<vuln vid="7a2e0063-0e4e-11e8-94c0-5453ed2e2b49">
<topic>p7zip-codec-rar -- insufficient error handling</topic>
<affects>
<package>
<name>p7zip-codec-rar</name>
<range><lt>16.02_1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>MITRE reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5996">
<p>Insufficient exception handling in the method
NCompress::NRar3::CDecoder::Code of 7-Zip before 18.00 and p7zip
can lead to multiple memory corruptions within the PPMd code,
alows remote attackers to cause a denial of service (segmentation
fault) or execute arbitrary code via a crafted RAR archive.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-5996</cvename>
<url>https://landave.io/2018/01/7-zip-multiple-memory-corruptions-via-rar-and-zip/</url>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5996</url>
<url>https://nvd.nist.gov/vuln/detail/CVE-2018-5996</url>
</references>
<dates>
<discovery>2018-01-23</discovery>
<entry>2018-02-10</entry>
</dates>
</vuln>
<vuln vid="6d337396-0e4a-11e8-94c0-5453ed2e2b49">
<topic>p7zip -- heap-based buffer overflow</topic>
<affects>
<package>
<name>p7zip</name>
<range><lt>16.02_1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>MITRE reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17969">
<p>Heap-based buffer overflow in the
NCompress::NShrink::CDecoder::CodeReal method in 7-Zip before
18.00 and p7zip allows remote attackers to cause a denial of
service (out-of-bounds write) or potentially execute arbitrary
code via a crafted ZIP archive.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-17969</cvename>
<url>https://landave.io/2018/01/7-zip-multiple-memory-corruptions-via-rar-and-zip/</url>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17969</url>
<url>https://nvd.nist.gov/vuln/detail/CVE-2017-17969</url>
<url>https://marc.info/?l=bugtraq&=151782582216805&=2</url>
</references>
<dates>
<discovery>2018-01-23</discovery>
<entry>2018-02-10</entry>
</dates>
</vuln>
<vuln vid="3ee6e521-0d32-11e8-99b0-d017c2987f9a">
<topic>mpv -- arbitrary code execution via crafted website</topic>
<affects>
<package>
<name>mpv</name>
<range><lt>0.27.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>mpv developers report:</p>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2018-6360">
<p>mpv through 0.28.0 allows remote attackers to execute arbitrary code
via a crafted web site, because it reads HTML documents containing
VIDEO elements, and accepts arbitrary URLs in a src attribute without
a protocol whitelist in player/lua/ytdl_hook.lua. For example, an
av://lavfi:ladspa=file= URL signifies that the product should call
dlopen on a shared object file located at an arbitrary local pathname.
The issue exists because the product does not consider that youtube-dl
can provide a potentially unsafe URL.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/mpv-player/mpv/issues/5456</url>
<cvename>CVE-2018-6360</cvename>
</references>
<dates>
<discovery>2018-01-28</discovery>
<entry>2018-02-09</entry>
<modified>2018-02-11</modified>
</dates>
</vuln>
<vuln vid="3d0eeef8-0cf9-11e8-99b0-d017c2987f9a">
<topic>Mailman -- Cross-site scripting (XSS) vulnerability in the web UI</topic>
<affects>
<package>
<name>mailman</name>
<range><lt>2.1.26</lt></range>
</package>
<package>
<name>mailman-with-htdig</name>
<range><lt>2.1.26</lt></range>
</package>
<package>
<name>ja-mailman</name>
<range><le>2.1.14.j7_3,1</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mark Sapiro reports:</p>
<blockquote cite="https://www.mail-archive.com/mailman-users@python.org/msg70478.html">
<p>An XSS vulnerability in the user options CGI could allow a crafted URL
to execute arbitrary javascript in a user's browser. A related issue
could expose information on a user's options page without requiring
login.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.mail-archive.com/mailman-users@python.org/msg70478.html</url>
<cvename>CVE-2018-5950</cvename>
</references>
<dates>
<discovery>2018-01-20</discovery>
<entry>2018-02-08</entry>
</dates>
</vuln>
<vuln vid="c602c791-0cf4-11e8-a2ec-6cc21735f730">
<topic>PostgreSQL vulnerabilities</topic>
<affects>
<package>
<name>postgresql93-server</name>
<range><ge>9.3.0</ge><lt>9.3.21</lt></range>
</package>
<package>
<name>postgresql94-server</name>
<range><ge>9.4.0</ge><lt>9.4.16</lt></range>
</package>
<package>
<name>postgresql95-server</name>
<range><ge>9.5.0</ge><lt>9.5.11</lt></range>
</package>
<package>
<name>postgresql96-server</name>
<range><ge>9.6.0</ge><lt>9.6.7</lt></range>
</package>
<package>
<name>postgresql10-server</name>
<range><ge>10.0</ge><lt>10.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The PostgreSQL project reports:</p>
<blockquote cite="https://www.postgresql.org/about/news/1829/">
<ul>
<li>CVE-2018-1052: Fix the processing of partition keys containing multiple expressions (only for PostgreSQL-10.x)</li>
<li>CVE-2018-1053: Ensure that all temporary files made with "pg_upgrade" are non-world-readable</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-1052</cvename>
<cvename>CVE-2018-1053</cvename>
</references>
<dates>
<discovery>2018-02-05</discovery>
<entry>2018-02-08</entry>
</dates>
</vuln>
<vuln vid="b38e8150-0535-11e8-96ab-0800271d4b9c">
<topic>tiff -- multiple vulnerabilities</topic>
<affects>
<package>
<name>tiff</name>
<range><le>4.0.9</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Debian Security Advisory reports:</p>
<blockquote cite="https://www.debian.org/security/2018/dsa-4100">
<p>Multiple vulnerabilities have been discovered in the libtiff library and the included tools, which may result in denial of service or the execution of arbitrary code.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-9935</cvename>
<url>http://bugzilla.maptools.org/show_bug.cgi?id=2704</url>
<cvename>CVE-2017-18013</cvename>
<url>http://bugzilla.maptools.org/show_bug.cgi?id=2770</url>
<bid>225544</bid>
</references>
<dates>
<discovery>2017-06-22</discovery>
<entry>2018-01-29</entry>
</dates>
</vuln>
<vuln vid="756a8631-0b84-11e8-a986-6451062f0f7a">
<topic>Flash Player -- multiple vulnerabilities</topic>
<affects>
<package>
<name>linux-flashplayer</name>
<range><lt>28.0.0.161</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Adobe reports:</p>
<blockquote cite="https://helpx.adobe.com/security/products/flash-player/apsb18-03.html">
<ul>
<li>This update resolves use-after-free vulnerabilities that
could lead to remote code execution (CVE-2018-4877,
CVE-2018-4878).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-4877</cvename>
<cvename>CVE-2018-4878</cvename>
<url>https://helpx.adobe.com/security/products/flash-player/apsa18-01.html</url>
<url>https://helpx.adobe.com/security/products/flash-player/apsb18-03.html</url>
</references>
<dates>
<discovery>2018-01-31</discovery>
<entry>2018-02-06</entry>
</dates>
</vuln>
<vuln vid="f5524753-67b1-4c88-8114-29c2d258b383">
<topic>mini_httpd,thttpd -- Buffer overflow in htpasswd</topic>
<affects>
<package>
<name>mini_httpd</name>
<range><lt>1.28</lt></range>
</package>
<package>
<name>thttpd</name>
<range><lt>2.28</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Alessio Santoru reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17663">
<p>Buffer overflow in htpasswd.</p>
</blockquote>
</body>
</description>
<references>
<url>http://acme.com/updates/archive/199.html</url>
</references>
<dates>
<discovery>2017-12-13</discovery>
<entry>2018-02-06</entry>
</dates>
</vuln>
<vuln vid="3746de31-0a1a-11e8-83e7-485b3931c969">
<topic>shadowsocks-libev -- command injection via shell metacharacters</topic>
<affects>
<package>
<name>shadowsocks-libev</name>
<range><ge>3.1.0</ge><lt>3.1.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>MITRE reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15924">
<p>Improper parsing allows command injection via shell metacharacters in
a JSON configuration request received via 127.0.0.1 UDP traffic.</p>
</blockquote>
</body>
</description>
<references>
<url>https://nvd.nist.gov/vuln/detail/CVE-2017-15924</url>
</references>
<dates>
<discovery>2017-10-27</discovery>
<entry>2018-02-05</entry>
</dates>
</vuln>
<vuln vid="5044bd23-08cb-11e8-b08f-00012e582166">
<topic>palemoon -- multiple vulnerabilities</topic>
<affects>
<package>
<name>palemoon</name>
<range><lt>27.7.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Pale Moon reports:</p>
<blockquote cite="http://www.palemoon.org/releasenotes.shtml">
<p>CVE-2018-5102: Use-after-free in HTML media elements</p>
<p>CVE-2018-5122: Potential integer overflow in DoCrypt</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-5102</cvename>
<cvename>CVE-2018-5122</cvename>
</references>
<dates>
<discovery>2018-01-23</discovery>
<entry>2018-02-03</entry>
</dates>
</vuln>
<vuln vid="d696473f-9f32-42c5-a106-bf4536fb1f74">
<topic>Django -- information leakage</topic>
<affects>
<package>
<name>py27-django111</name>
<name>py34-django111</name>
<name>py35-django111</name>
<name>py36-django111</name>
<range><lt>1.11.10</lt></range>
</package>
<package>
<name>py27-django20</name>
<name>py34-django20</name>
<name>py35-django20</name>
<name>py36-django20</name>
<range><lt>2.0.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Django release notes:</p>
<blockquote cite="https://docs.djangoproject.com/en/1.11/releases/1.11.10/">
<p>CVE-2018-6188: Information leakage in AuthenticationForm</p>
<p>A regression in Django 1.11.8 made AuthenticationForm run its
confirm_login_allowed() method even if an incorrect password is entered.
This can leak information about a user, depending on what messages
confirm_login_allowed() raises. If confirm_login_allowed() isn't
overridden, an attacker enter an arbitrary username and see if that user
has been set to is_active=False. If confirm_login_allowed() is
overridden, more sensitive details could be leaked.</p>
<p>This issue is fixed with the caveat that AuthenticationForm can no
longer raise the "This account is inactive." error if the authentication
backend rejects inactive users (the default authentication backend,
ModelBackend, has done that since Django 1.10). This issue will be
revisited for Django 2.1 as a fix to address the caveat will likely be too
invasive for inclusion in older versions.</p>
</blockquote>
</body>
</description>
<references>
<url>https://docs.djangoproject.com/en/1.11/releases/1.11.10/</url>
<url>https://docs.djangoproject.com/en/2.0/releases/2.0.2/</url>
<cvename>CVE-2018-6188</cvename>
</references>
<dates>
<discovery>2018-02-01</discovery>
<entry>2018-02-02</entry>
</dates>
</vuln>
<vuln vid="e72d5bf5-07a0-11e8-8248-0021ccb9e74d">
<topic>w3m - multiple vulnerabilities</topic>
<affects>
<package>
<name>w3m</name>
<name>w3m-img</name>
<name>ja-w3m</name>
<name>ja-w3m-img</name>
<range><lt>0.5.3.20180125</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Tatsuya Kinoshita reports:</p>
<blockquote cite="https://github.com/tats/w3m/commit/01d41d49b273a8cc75b27c6ab42291b46004fc0c">
<p>CVE-2018-6196 * table.c: Prevent negative indent value in feed_table_block_tag().</p>
<p>CVE-2018-6197 * form.c: Prevent invalid columnPos() call in formUpdateBuffer().</p>
<p>CVE-2018-6198 * config.h.dist, config.h.in, configure, configure.ac, main.c, rc.c: Make temporary directory safely when ~/.w3m is unwritable.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/tats/w3m/commit/e773a0e089276f82c546447c0fd1e6c0f9156628</url>
<cvename>CVE-2018-6196</cvename>
<cvename>CVE-2018-6197</cvename>
<cvename>CVE-2018-6198</cvename>
</references>
<dates>
<discovery>2018-01-25</discovery>
<entry>2018-02-01</entry>
<modified>2018-02-03</modified>
</dates>
</vuln>
<vuln vid="103bf96a-6211-45ab-b567-1555ebb3a86a">
<topic>firefox -- Arbitrary code execution through unsanitized browser UI</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>58.0.1,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.0.3.65</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-05/">
<p>Mozilla developer <strong>Johann Hofmann</strong> reported that
unsanitized output in the browser UI can lead to arbitrary
code execution.</p>
</blockquote>
</body>
</description>
<references>
<url>https://bugzilla.mozilla.org/show_bug.cgi?id=1432966</url>
</references>
<dates>
<discovery>2018-01-29</discovery>
<entry>2018-01-29</entry>
<modified>2018-01-31</modified>
</dates>
</vuln>
<vuln vid="2cceb80e-c482-4cfd-81b3-2088d2c0ad53">
<topic>gcab -- stack overflow</topic>
<affects>
<package>
<name>gcab</name>
<range><lt>0.8</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Upstream reports:</p>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2018-5345">
<p>A stack-based buffer overflow within GNOME gcab through
0.7.4 can be exploited by malicious attackers to cause a
crash or, potentially, execute arbitrary code via a
crafted .cab file.</p>
</blockquote>
</body>
</description>
<references>
<url>https://nvd.nist.gov/vuln/detail/CVE-2018-5345</url>
<url>https://mail.gnome.org/archives/ftp-release-list/2018-January/msg00066.html</url>
<cvename>CVE-2018-5345</cvename>
</references>
<dates>
<discovery>2018-01-23</discovery>
<entry>2018-01-27</entry>
</dates>
</vuln>
<vuln vid="92b8b284-a3a2-41b1-956c-f9cf8b74f500">
<topic>dovecot -- abort of SASL authentication results in a memory leak</topic>
<affects>
<package>
<name>dovecot</name>
<range><gt>2.0</gt><le>2.2.33.2_3</le></range>
<range><ge>2.3</ge><le>2.3.0</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p> Pedro Sampaio reports:</p>
<blockquote cite="https://bugzilla.redhat.com/show_bug.cgi?id=1532768">
<p>A flaw was found in dovecot 2.0 up to 2.2.33 and 2.3.0. A abort of
SASL authentication results in a memory leak in Dovecot auth client
used by login processes. The leak has impact in high performance
configuration where same login processes are reused and can cause the
process to crash due to memory exhaustion.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-15132</cvename>
<url>https://bugzilla.redhat.com/show_bug.cgi?id=1532768</url>
<url>https://github.com/dovecot/core/commit/1a29ed2f96da1be22fa5a4d96c7583aa81b8b060.patch</url>
</references>
<dates>
<discovery>2018-01-09</discovery>
<entry>2018-01-26</entry>
<modified>2018-02-01</modified>
</dates>
</vuln>
<vuln vid="0cbf0fa6-dcb7-469c-b87a-f94cffd94583">
<topic>cURL -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>curl</name>
<range><lt>7.58.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The cURL project reports:</p>
<blockquote cite="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000007">
<p>libcurl 7.1 through 7.57.0 might accidentally leak authentication
data to third parties. When asked to send custom headers in its HTTP
requests, libcurl will send that set of headers first to the host in
the initial URL but also, if asked to follow redirects and a 30X HTTP
response code is returned, to the host mentioned in URL in the
`Location:` response header value. Sending the same set of headers to
subsequest hosts is in particular a problem for applications that pass
on custom `Authorization:` headers, as this header often contains
privacy sensitive information or data that could allow others to
impersonate the libcurl-using client's request.</p>
</blockquote>
</body>
</description>
<references>
<url>https://curl.haxx.se/docs/adv_2018-b3bf.html</url>
<cvename>CVE-2018-1000007</cvename>
</references>
<dates>
<discovery>2018-01-24</discovery>
<entry>2018-01-26</entry>
</dates>
</vuln>
<vuln vid="b464f61b-84c7-4e1c-8ad4-6cf9efffd025">
<topic>clamav -- multiple vulnerabilities</topic>
<affects>
<package>
<name>clamav</name>
<range><lt>0.99.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>ClamAV project reports:</p>
<blockquote cite="http://blog.clamav.net/2018/01/clamav-0993-has-been-released.html">
<p>Join us as we welcome ClamAV 0.99.3 to the family!.</p>
<p>This release is a security release and is recommended for
all ClamAV users.</p>
<p>CVE-2017-12374 ClamAV UAF (use-after-free) Vulnerabilities</p>
<p>CVE-2017-12375 ClamAV Buffer Overflow Vulnerability</p>
<p>CVE-2017-12376 ClamAV Buffer Overflow in handle_pdfname
Vulnerability</p>
<p>CVE-2017-12377 ClamAV Mew Packet Heap Overflow Vulnerability</p>
<p>CVE-2017-12378 ClamAV Buffer Over Read Vulnerability</p>
<p>CVE-2017-12379 ClamAV Buffer Overflow in messageAddArgument
Vulnerability</p>
<p>CVE-2017-12380 ClamAV Null Dereference Vulnerability</p>
</blockquote>
</body>
</description>
<references>
<url>http://blog.clamav.net/2018/01/clamav-0993-has-been-released.html</url>
<cvename>CVE-2017-12374</cvename>
<cvename>CVE-2017-12375</cvename>
<cvename>CVE-2017-12376</cvename>
<cvename>CVE-2017-12377</cvename>
<cvename>CVE-2017-12378</cvename>
<cvename>CVE-2017-12379</cvename>
<cvename>CVE-2017-12380</cvename>
</references>
<dates>
<discovery>2018-01-25</discovery>
<entry>2018-01-26</entry>
</dates>
</vuln>
<vuln vid="a891c5b4-3d7a-4de9-9c71-eef3fd698c77">
<topic>mozilla -- multiple vulnerabilities</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>58.0_1,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.0.3.63</lt></range>
</package>
<package>
<name>seamonkey</name>
<name>linux-seamonkey</name>
<range><lt>2.49.2</lt></range>
</package>
<package>
<name>firefox-esr</name>
<range><lt>52.6.0_1,1</lt></range>
</package>
<package>
<name>linux-firefox</name>
<range><lt>52.6.0,2</lt></range>
</package>
<package>
<name>libxul</name>
<name>thunderbird</name>
<name>linux-thunderbird</name>
<range><lt>52.6.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-02/">
<p>CVE-2018-5091: Use-after-free with DTMF timers</p>
<p>CVE-2018-5092: Use-after-free in Web Workers</p>
<p>CVE-2018-5093: Buffer overflow in WebAssembly during Memory/Table resizing</p>
<p>CVE-2018-5094: Buffer overflow in WebAssembly with garbage collection on uninitialized memory</p>
<p>CVE-2018-5095: Integer overflow in Skia library during edge builder allocation</p>
<p>CVE-2018-5097: Use-after-free when source document is manipulated during XSLT</p>
<p>CVE-2018-5098: Use-after-free while manipulating form input elements</p>
<p>CVE-2018-5099: Use-after-free with widget listener</p>
<p>CVE-2018-5100: Use-after-free when IsPotentiallyScrollable arguments are freed from memory</p>
<p>CVE-2018-5101: Use-after-free with floating first-letter style elements</p>
<p>CVE-2018-5102: Use-after-free in HTML media elements</p>
<p>CVE-2018-5103: Use-after-free during mouse event handling</p>
<p>CVE-2018-5104: Use-after-free during font face manipulation</p>
<p>CVE-2018-5105: WebExtensions can save and execute files on local file system without user prompts</p>
<p>CVE-2018-5106: Developer Tools can expose style editor information cross-origin through service worker</p>
<p>CVE-2018-5107: Printing process will follow symlinks for local file access</p>
<p>CVE-2018-5108: Manually entered blob URL can be accessed by subsequent private browsing tabs</p>
<p>CVE-2018-5109: Audio capture prompts and starts with incorrect origin attribution</p>
<p>CVE-2018-5110: Cursor can be made invisible on OS X</p>
<p>CVE-2018-5111: URL spoofing in addressbar through drag and drop</p>
<p>CVE-2018-5112: Extension development tools panel can open a non-relative URL in the panel</p>
<p>CVE-2018-5113: WebExtensions can load non-HTTPS pages with browser.identity.launchWebAuthFlow</p>
<p>CVE-2018-5114: The old value of a cookie changed to HttpOnly remains accessible to scripts</p>
<p>CVE-2018-5115: Background network requests can open HTTP authentication in unrelated foreground tabs</p>
<p>CVE-2018-5116: WebExtension ActiveTab permission allows cross-origin frame content access</p>
<p>CVE-2018-5117: URL spoofing with right-to-left text aligned left-to-right</p>
<p>CVE-2018-5118: Activity Stream images can attempt to load local content through file:</p>
<p>CVE-2018-5119: Reader view will load cross-origin content in violation of CORS headers</p>
<p>CVE-2018-5121: OS X Tibetan characters render incompletely in the addressbar</p>
<p>CVE-2018-5122: Potential integer overflow in DoCrypt</p>
<p>CVE-2018-5090: Memory safety bugs fixed in Firefox 58</p>
<p>CVE-2018-5089: Memory safety bugs fixed in Firefox 58 and Firefox ESR 52.6</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-5089</cvename>
<cvename>CVE-2018-5090</cvename>
<cvename>CVE-2018-5091</cvename>
<cvename>CVE-2018-5092</cvename>
<cvename>CVE-2018-5093</cvename>
<cvename>CVE-2018-5094</cvename>
<cvename>CVE-2018-5095</cvename>
<cvename>CVE-2018-5097</cvename>
<cvename>CVE-2018-5098</cvename>
<cvename>CVE-2018-5099</cvename>
<cvename>CVE-2018-5100</cvename>
<cvename>CVE-2018-5101</cvename>
<cvename>CVE-2018-5102</cvename>
<cvename>CVE-2018-5103</cvename>
<cvename>CVE-2018-5104</cvename>
<cvename>CVE-2018-5105</cvename>
<cvename>CVE-2018-5106</cvename>
<cvename>CVE-2018-5107</cvename>
<cvename>CVE-2018-5108</cvename>
<cvename>CVE-2018-5109</cvename>
<cvename>CVE-2018-5110</cvename>
<cvename>CVE-2018-5111</cvename>
<cvename>CVE-2018-5112</cvename>
<cvename>CVE-2018-5113</cvename>
<cvename>CVE-2018-5114</cvename>
<cvename>CVE-2018-5115</cvename>
<cvename>CVE-2018-5116</cvename>
<cvename>CVE-2018-5117</cvename>
<cvename>CVE-2018-5118</cvename>
<cvename>CVE-2018-5119</cvename>
<cvename>CVE-2018-5121</cvename>
<cvename>CVE-2018-5122</cvename>
<url>https://www.mozilla.org/security/advisories/mfsa2018-02/</url>
<url>https://www.mozilla.org/security/advisories/mfsa2018-03/</url>
</references>
<dates>
<discovery>2018-01-23</discovery>
<entry>2018-01-23</entry>
<modified>2018-01-29</modified>
</dates>
</vuln>
<vuln vid="24a82876-002e-11e8-9a95-0cc47a02c232">
<topic>powerdns-recursor -- insufficient validation of DNSSEC signatures</topic>
<affects>
<package>
<name>powerdns-recursor</name>
<range><lt>4.1.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>PowerDNS Security Advisory reports:</p>
<blockquote cite="https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2018-01.html">
<p>An issue has been found in the DNSSEC validation component of
PowerDNS Recursor, allowing an ancestor delegation NSEC or NSEC3
record to be used to wrongfully prove the non-existence of a RR
below the owner name of that record. This would allow an attacker in
position of man-in-the-middle to send a NXDOMAIN answer for a name
that does exist.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-1000003</cvename>
<url>https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2018-01.html</url>
</references>
<dates>
<discovery>2018-01-22</discovery>
<entry>2018-01-23</entry>
</dates>
</vuln>
<vuln vid="e264e74e-ffe0-11e7-8b91-e8e0b747a45a">
<topic>chromium -- multiple vulnerabilities</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>63.0.3239.108</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop_14.html">
<p>2 security fixes in this release, including:</p>
<ul>
<li>[788453] High CVE-2017-15429: UXSS in V8. Reported by
Anonymous on 2017-11-24</li>
<li>[794792] Various fixes from internal audits, fuzzing and other initiatives</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-15429</cvename>
<url>https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop_14.html</url>
</references>
<dates>
<discovery>2017-12-14</discovery>
<entry>2018-01-23</entry>
</dates>
</vuln>
<vuln vid="1d951e85-ffdb-11e7-8b91-e8e0b747a45a">
<topic>chromium -- multiple vulnerabilities</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>63.0.3239.84</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html">
<p>37 security fixes in this release, including:</p>
<ul>
<li>[778505] Critical CVE-2017-15407: Out of bounds write in QUIC. Reported by
Ned Williamson on 2017-10-26</li>
<li>[762374] High CVE-2017-15408: Heap buffer overflow in PDFium. Reported by
Ke Liu of Tencent's Xuanwu LAB on 2017-09-06</li>
<li>[763972] High CVE-2017-15409: Out of bounds write in Skia. Reported by
Anonymous on 2017-09-11</li>
<li>[765921] High CVE-2017-15410: Use after free in PDFium. Reported by
Luat Nguyen of KeenLab, Tencent on 2017-09-16</li>
<li>[770148] High CVE-2017-15411: Use after free in PDFium. Reported by
Luat Nguyen of KeenLab, Tencent on 2017-09-29</li>
<li>[727039] High CVE-2017-15412: Use after free in libXML. Reported by
Nick Wellnhofer on 2017-05-27</li>
<li>[766666] High CVE-2017-15413: Type confusion in WebAssembly. Reported by
Gaurav Dewan of Adobe Systems India Pvt. Ltd. on 2017-09-19</li>
<li>[765512] Medium CVE-2017-15415: Pointer information disclosure in IPC call.
Reported by Viktor Brange of Microsoft Offensive Security Research Team on 2017-09-15</li>
<li>[779314] Medium CVE-2017-15416: Out of bounds read in Blink. Reported by
Ned Williamson on 2017-10-28</li>
<li>[699028] Medium CVE-2017-15417: Cross origin information disclosure in Skia.
Reported by Max May on 2017-03-07</li>
<li>[765858] Medium CVE-2017-15418: Use of uninitialized value in Skia. Reported by
Kushal Arvind Shah of Fortinet's FortiGuard Labs on 2017-09-15</li>
<li>[780312] Medium CVE-2017-15419: Cross origin leak of redirect URL in Blink.
Reported by Jun Kokatsu on 2017-10-31</li>
<li>[777419] Medium CVE-2017-15420: URL spoofing in Omnibox. Reported by
WenXu Wu of Tencent's Xuanwu Lab on 2017-10-23</li>
<li>[774382] Medium CVE-2017-15422: Integer overflow in ICU. Reported by
Yuan Deng of Ant-financial Light-Year Security Lab on 2017-10-13</li>
<li>[780484] Medium CVE-2017-15430: Unsafe navigation in Chromecast Plugin.
Reported by jinmo123 on 2017-01-11</li>
<li>[778101] Low CVE-2017-15423: Issue with SPAKE implementation in BoringSSL.
Reported by Greg Hudson on 2017-10-25</li>
<li>[756226] Low CVE-2017-15424: URL Spoof in Omnibox. Reported by
Khalil Zhani on 2017-08-16</li>
<li>[756456] Low CVE-2017-15425: URL Spoof in Omnibox. Reported by
xisigr of Tencent's Xuanwu Lab on 2017-08-17</li>
<li>[757735] Low CVE-2017-15426: URL Spoof in Omnibox. Reported by
WenXu Wu of Tencent's Xuanwu Lab on 2017-08-18</li>
<li>[768910] Low CVE-2017-15427: Insufficient blocking of Javascript in Omnibox.
Reported by Junaid Farhan on 2017-09-26</li>
<li>[792099] Various fixes from internal audits, fuzzing and other initiatives</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-15407</cvename>
<cvename>CVE-2017-15408</cvename>
<cvename>CVE-2017-15409</cvename>
<cvename>CVE-2017-15410</cvename>
<cvename>CVE-2017-15411</cvename>
<cvename>CVE-2017-15412</cvename>
<cvename>CVE-2017-15413</cvename>
<cvename>CVE-2017-15415</cvename>
<cvename>CVE-2017-15416</cvename>
<cvename>CVE-2017-15417</cvename>
<cvename>CVE-2017-15418</cvename>
<cvename>CVE-2017-15419</cvename>
<cvename>CVE-2017-15420</cvename>
<cvename>CVE-2017-15422</cvename>
<cvename>CVE-2017-15430</cvename>
<cvename>CVE-2017-15423</cvename>
<cvename>CVE-2017-15424</cvename>
<cvename>CVE-2017-15425</cvename>
<cvename>CVE-2017-15426</cvename>
<cvename>CVE-2017-15427</cvename>
<url>https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html</url>
</references>
<dates>
<discovery>2017-12-06</discovery>
<entry>2018-01-23</entry>
</dates>
</vuln>
<vuln vid="82894193-ffd4-11e7-8b91-e8e0b747a45a">
<topic>chromium -- out of bounds read</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>62.0.3202.94</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2017/11/stable-channel-update-for-desktop_13.html">
<p>1 security fix in this release, including:</p>
<ul>
<li>[782145] High CVE-2017-15428: Out of bounds read in V8. Reported by
Zhao Qixun of Qihoo 360 Vulcan Team on 2017-11-07</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2017-15428</cvename>
<url>https://chromereleases.googleblog.com/2017/11/stable-channel-update-for-desktop_13.html</url>
</references>
<dates>
<discovery>2017-11-13</discovery>
<entry>2018-01-23</entry>
</dates>
</vuln>
<vuln vid="8d3bae09-fd28-11e7-95f2-005056925db4">
<topic>unbound -- vulnerability in the processing of wildcard synthesized NSEC records</topic>
<affects>
<package>
<name>unbound</name>
<range><lt>1.6.8</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Unbound reports:</p>
<blockquote cite="https://unbound.net/downloads/CVE-2017-15105.txt">
<p>We discovered a vulnerability in the processing of wildcard synthesized
NSEC records. While synthesis of NSEC records is allowed by RFC4592,
these synthesized owner names should not be used in the NSEC processing.
This does, however, happen in Unbound 1.6.7 and earlier versions.</p>
</blockquote>
</body>
</description>
<references>
<url>https://unbound.net/downloads/CVE-2017-15105.txt</url>
<cvename>CVE-2017-15105</cvename>
<freebsdpr>ports/225313</freebsdpr>
</references>
<dates>
<discovery>2017-10-08</discovery>
<entry>2018-01-19</entry>
</dates>
</vuln>
<vuln vid="8e89a89a-fd15-11e7-bdf6-00e04c1ea73d">
<topic>phpbb3 -- multiple issues</topic>
<affects>
<package>
<name>phpbb3</name>
<range><lt>3.2.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>phpbb developers reports:</p>
<blockquote cite="https://wiki.phpbb.com/Release_Highlights/3.2.2">
<p>Password updater working with PostgreSQL - The cron for updating legacy password hashes was running invalid queries on PostgreSQL.</p>
<p>Deleting orphaned attachments w/ large number of orphaned attachments - Orphaned attachment deletion was improved to be able to delete them when a large number of orphaned attachments exist.</p>
<p>Multiple bugfixes for retrieving image size - Multiple issues with retrieving the image size of JPEGs and temporary files were resolved.</p>
<p>Issues with updating from phpBB 3.0.6 - Inconsistencies in the way parent modules were treated caused issues with updating from older phpBB 3.0 versions.</p>
<p>Forum / topic icon blurriness - Fixed issues with forum and topic icons looking blurry on some browsers.</p>
</blockquote>
</body>
</description>
<references>
<url>https://wiki.phpbb.com/Release_Highlights/3.2.2</url>
</references>
<dates>
<discovery>2018-01-07</discovery>
<entry>2018-01-19</entry>
</dates>
</vuln>
<vuln vid="e3445736-fd01-11e7-ac58-b499baebfeaf">
<topic>MySQL -- multiple vulnerabilities</topic>
<affects>
<package>
<name>mariadb55-server</name>
<range><lt>5.5.59</lt></range>
</package>
<package>
<name>mariadb100-server</name>
<range><lt>10.0.34</lt></range>
</package>
<package>
<name>mariadb101-server</name>
<range><lt>10.1.31</lt></range>
</package>
<package>
<name>mariadb102-server</name>
<range><lt>10.2.13</lt></range>
</package>
<package>
<name>mysql55-server</name>
<range><lt>5.5.59</lt></range>
</package>
<package>
<name>mysql56-server</name>
<range><lt>5.6.39</lt></range>
</package>
<package>
<name>mysql57-server</name>
<range><lt>5.7.21</lt></range>
</package>
<package>
<name>percona55-server</name>
<range><lt>5.5.59</lt></range>
</package>
<package>
<name>percona56-server</name>
<range><lt>5.6.39</lt></range>
</package>
<package>
<name>percona57-server</name>
<range><lt>5.7.21</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Oracle reports:</p>
<blockquote cite="http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html#AppendixMSQL">
<p>Not all vulnerabilities are relevant for all flavors/versions of the
servers and clients</p>
<ul>
<li>Vulnerability allows low privileged attacker with network access
via multiple protocols to compromise MySQL Server. Successful attacks
of this vulnerability can result in unauthorized ability to cause a
hang or frequently repeatable crash (complete DOS) of MySQL Server.
GIS: CVE-2018-2573, DDL CVE-2018-2622, Optimizer: CVE-2018-2640,
CVE-2018-2665, CVE-2018-2668, Security:Privileges: CVE-2018-2703,
Partition: CVE-2018-2562.</li>
<li>Vulnerability allows high privileged attacker with network access
via multiple protocols to compromise MySQL Server. Successful attacks
of this vulnerability can result in unauthorized ability to cause a
hang or frequently repeatable crash (complete DOS) of MySQL Server.
InnoDB: CVE-2018-2565, CVE-2018-2612 DML: CVE-2018-2576,
CVE-2018-2646, Stored Procedure: CVE-2018-2583, Performance Schema:
CVE-2018-2590, Partition: CVE-2018-2591, Optimizer: CVE-2018-2600,
CVE-2018-2667, Security:Privileges: CVE-2018-2696, Replication:
CVE-2018-2647.</li>
<li>Vulnerability allows a low or high privileged attacker with network
access via multiple protocols to compromise MySQL Server with
unauthorized creation, deletion, modification or access to data/
critical data. InnoDB: CVE-2018-2612, Performance Schema:
CVE-2018-2645, Replication: CVE-2018-2647, Partition: CVE-2018-2562.
</li>
</ul>
</blockquote>
</body>
</description>
<references>
<url>http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html#AppendixMSQL</url>
<url>https://mariadb.com/kb/en/library/mariadb-5559-release-notes/</url>
<cvename>CVE-2018-2562</cvename>
<cvename>CVE-2018-2565</cvename>
<cvename>CVE-2018-2573</cvename>
<cvename>CVE-2018-2576</cvename>
<cvename>CVE-2018-2583</cvename>
<cvename>CVE-2018-2586</cvename>
<cvename>CVE-2018-2590</cvename>
<cvename>CVE-2018-2591</cvename>
<cvename>CVE-2018-2600</cvename>
<cvename>CVE-2018-2612</cvename>
<cvename>CVE-2018-2622</cvename>
<cvename>CVE-2018-2640</cvename>
<cvename>CVE-2018-2645</cvename>
<cvename>CVE-2018-2646</cvename>
<cvename>CVE-2018-2647</cvename>
<cvename>CVE-2018-2665</cvename>
<cvename>CVE-2018-2667</cvename>
<cvename>CVE-2018-2668</cvename>
<cvename>CVE-2018-2696</cvename>
<cvename>CVE-2018-2703</cvename>
</references>
<dates>
<discovery>2017-01-18</discovery>
<entry>2018-01-19</entry>
</dates>
</vuln>
<vuln vid="c04dc18f-fcde-11e7-bdf6-00e04c1ea73d">
<topic>wordpress -- multiple issues</topic>
<affects>
<package>
<name>wordpress</name>
<name>fr-wordpress</name>
<range><lt>4.9.2,1</lt></range>
</package>
<package>
<name>de-wordpress</name>
<name>ja-wordpress</name>
<name>ru-wordpress</name>
<name>zh-wordpress-zh_CN</name>
<name>zh-wordpress-zh_TW</name>
<range><lt>4.9.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>wordpress developers reports:</p>
<blockquote cite="https://wordpress.org/news/2018/01/wordpress-4-9-2-security-and-maintenance-release/">
<p>JavaScript errors that prevented saving posts in Firefox have been fixed.</p>
<p>The previous taxonomy-agnostic behavior of get_category_link() and category_description() was restored.</p>
<p>Switching themes will now attempt to restore previous widget assignments, even when there are no sidebars to map.</p>
</blockquote>
</body>
</description>
<references>
<url>https://wordpress.org/news/2018/01/wordpress-4-9-2-security-and-maintenance-release/</url>
</references>
<dates>
<discovery>2018-01-16</discovery>
<entry>2018-01-19</entry>
</dates>
</vuln>
<vuln vid="65fab89f-2231-46db-8541-978f4e87f32a">
<topic>gitlab -- Remote code execution on project import</topic>
<affects>
<package>
<name>gitlab</name>
<range><lt>10.1.6</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>GitLab developers report:</p>
<blockquote cite="https://about.gitlab.com/2018/01/16/gitlab-10-dot-3-dot-4-released/">
<p>Today we are releasing versions 10.3.4, 10.2.6, and 10.1.6 for
GitLab Community Edition (CE) and Enterprise Edition (EE).</p>
<p>These versions contain a number of important security fixes,
including two that prevent remote code execution, and we strongly
recommend that all GitLab installations be upgraded to one of these
versions immediately.</p>
</blockquote>
</body>
</description>
<references>
<url>https://about.gitlab.com/2018/01/16/gitlab-10-dot-3-dot-4-released/</url>
<cvename>CVE-2017-0915</cvename>
<cvename>CVE-2018-3710</cvename>
</references>
<dates>
<discovery>2018-01-16</discovery>
<entry>2018-01-17</entry>
</dates>
</vuln>
<vuln vid="3e5b8bd3-0c32-452f-a60e-beab7b762351">
<topic>transmission-daemon -- vulnerable to dns rebinding attacks</topic>
<affects>
<package>
<name>transmission-daemon</name>
<range><le>2.92_3</le></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google Project Zero reports:</p>
<blockquote cite="https://bugs.chromium.org/p/project-zero/issues/detail?id=1447">
<p>The transmission bittorrent client uses a client/server
architecture, the user interface is the client which communicates
to the worker daemon using JSON RPC requests.</p>
<p>As with all HTTP RPC schemes like this, any website can send
requests to the daemon listening on localhost with XMLHttpRequest(),
but the theory is they will be ignored because clients must prove
they can read and set a specific header, X-Transmission-Session-Id.
Unfortunately, this design doesn't work because of an attack called
"DNS rebinding". Any website can simply create a dns name that they
are authorized to communicate with, and then make it resolve to
localhost.</p>
<p>Exploitation is simple, you could set script-torrent-done-enabled
and run any command, or set download-dir to /home/user/ and then
upload a torrent for .bashrc.</p>
</blockquote>
</body>
</description>
<references>
<url>https://bugs.chromium.org/p/project-zero/issues/detail?id=1447</url>
<url>https://github.com/transmission/transmission/pull/468</url>
</references>
<dates>
<discovery>2017-11-30</discovery>
<entry>2018-01-14</entry>
</dates>
</vuln>
<vuln vid="3dbe9492-f7b8-11e7-a12d-6cc21735f730">
<topic>shibboleth-sp -- vulnerable to forged user attribute data</topic>
<affects>
<package>
<name>xmltooling</name>
<range><lt>1.6.3</lt></range>
</package>
<package>
<name>xerces-c3</name>
<range><lt>3.1.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Shibboleth consortium reports:</p>
<blockquote cite="https://shibboleth.net/community/advisories/secadv_20180112.txt">
<p>
Shibboleth SP software vulnerable to forged user attribute data
</p>
<p>
The Service Provider software relies on a generic XML parser to
process SAML responses and there are limitations in older versions
of the parser that make it impossible to fully disable Document Type
Definition (DTD) processing.
</p>
<p>
Through addition/manipulation of a DTD, it's possible to make
changes to an XML document that do not break a digital signature but
are mishandled by the SP and its libraries. These manipulations can
alter the user data passed through to applications behind the SP and
result in impersonation attacks and exposure of protected
information.
</p>
<p>
While newer versions of the xerces-c3 parser are configured by the
SP into disallowing the use of a DTD via an environment variable,
this feature is not present in the xerces-c3 parser before version
3.1.4, so an additional fix is being provided now that an actual DTD
exploit has been identified. Xerces-c3-3.1.4 was committed to the
ports tree already on 2016-07-26.
</p>
</blockquote>
</body>
</description>
<references>
<url>https://shibboleth.net/community/advisories/secadv_20180112.txt</url>
<cvename>CVE-2018-0486</cvename>
</references>
<dates>
<discovery>2018-01-12</discovery>
<entry>2018-01-12</entry>
</dates>
</vuln>
<vuln vid="9c016563-f582-11e7-b33c-6451062f0f7a">
<topic>Flash Player -- information disclosure</topic>
<affects>
<package>
<name>linux-flashplayer</name>
<range><lt>28.0.0.137</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Adobe reports:</p>
<blockquote cite="https://helpx.adobe.com/security/products/flash-player/apsb18-01.html">
<ul>
<li>This update resolves an out-of-bounds read vulnerability that
could lead to information disclosure (CVE-2018-4871).</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-4871</cvename>
<url>https://helpx.adobe.com/security/products/flash-player/apsb18-01.html</url>
</references>
<dates>
<discovery>2018-01-09</discovery>
<entry>2018-01-09</entry>
</dates>
</vuln>
<vuln vid="4055aee5-f4c6-11e7-95f2-005056925db4">
<topic>awstats -- remote code execution</topic>
<affects>
<package>
<name>awstats</name>
<range><lt>7.7,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mitre reports:</p>
<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000501">
<p>Awstats version 7.6 and earlier is vulnerable to a path traversal
flaw in the handling of the "config" and "migrate" parameters resulting
in unauthenticated remote code execution.</p>
</blockquote>
</body>
</description>
<references>
<url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000501</url>
<cvename>CVE-2017-1000501</cvename>
<freebsdpr>ports/225007</freebsdpr>
</references>
<dates>
<discovery>2018-01-03</discovery>
<entry>2018-01-08</entry>
</dates>
</vuln>
<vuln vid="a3764767-f31e-11e7-95f2-005056925db4">
<topic>irssi -- multiple vulnerabilities</topic>
<affects>
<package>
<name>irssi</name>
<range><lt>1.0.6,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Irssi reports:</p>
<blockquote cite="https://irssi.org/security/irssi_sa_2018_01.txt">
<p>When the channel topic is set without specifying a sender, Irssi
may dereference NULL pointer. Found by Joseph Bisch.</p>
<p>When using incomplete escape codes, Irssi may access data beyond
the end of the string. Found by Joseph Bisch.</p>
<p>A calculation error in the completion code could cause a heap
buffer overflow when completing certain strings.
Found by Joseph Bisch.</p>
<p>When using an incomplete variable argument, Irssi may access data
beyond the end of the string. Found by Joseph Bisch.</p>
</blockquote>
</body>
</description>
<references>
<url>https://irssi.org/security/irssi_sa_2018_01.txt</url>
<cvename>CVE-2018-5205</cvename>
<cvename>CVE-2018-5206</cvename>
<cvename>CVE-2018-5207</cvename>
<cvename>CVE-2018-5208</cvename>
<freebsdpr>ports/224954</freebsdpr>
</references>
<dates>
<discovery>2018-01-03</discovery>
<entry>2018-01-06</entry>
</dates>
</vuln>
<vuln vid="8429711b-76ca-474e-94a0-6b980f1e2d47">
<topic>mozilla -- Speculative execution side-channel attack</topic>
<affects>
<package>
<name>firefox</name>
<range><lt>57.0.4,1</lt></range>
</package>
<package>
<name>waterfox</name>
<range><lt>56.0.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Mozilla Foundation reports:</p>
<blockquote cite="https://www.mozilla.org/en-US/security/advisories/mfsa2018-01/">
<p><strong>Jann Horn</strong> of Google Project Zero
Security reported that speculative execution performed
by modern CPUs could leak information through a timing
side-channel attack. Microsoft Vulnerability Research
extended this attack to browser JavaScript engines and
demonstrated that code on a malicious web page could
read data from other web sites (violating the
same-origin policy) or private data from the browser
itself.</p>
<p>Since this new class of attacks involves measuring
precise time intervals, as a parti al, short-term,
mitigation we are disabling or reducing the precision of
several time sources in Firefox. The precision of
<code>performance.now()</code> has been reduced from 5μs
to 20μs, and the <code>SharedArrayBuffer</code> feature
has been disabled because it can be used to construct a
high-resolution timer.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.mozilla.org/security/advisories/mfsa2018-01/</url>
</references>
<dates>
<discovery>2018-01-04</discovery>
<entry>2018-01-05</entry>
</dates>
</vuln>
