Author: buildbot
Date: Mon Jul 29 15:22:27 2019
New Revision: 1048218
Log:
Staging update by buildbot for vcl
Modified:
websites/staging/vcl/trunk/content/ (props changed)
websites/staging/vcl/trunk/content/security.html
Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul 29 15:22:27 2019
@@ -1 +1 @@
-1863947
+1863948
Modified: websites/staging/vcl/trunk/content/security.html
==============================================================================
--- websites/staging/vcl/trunk/content/security.html (original)
+++ websites/staging/vcl/trunk/content/security.html Mon Jul 29 15:22:27 2019
@@ -106,15 +106,15 @@ h2:hover > .headerlink, h3:hover > .head
visibility: hidden;
}
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
-<h1 id="h1-security-issues">h1 Security Issues<a class="headerlink"
href="#h1-security-issues" title="Permanent link">¶</a></h1>
+<h1 id="security-issues">Security Issues<a class="headerlink"
href="#security-issues" title="Permanent link">¶</a></h1>
<p>The Apache Software Foundation takes security issues seriously and has a
<a href="https://www.apache.org/security/";>security team</a> that helps Apache
projects work through security
issues. If you discover any potential vulnerabilities in Apache VCL, please
report them to
<a href="mailto:[email protected]";>[email protected]</a>.</p>
-<h1 id="h2-known-security-issues">h2 Known Security Issues<a
class="headerlink" href="#h2-known-security-issues" title="Permanent
link">¶</a></h1>
+<h2 id="known-security-issues">Known Security Issues<a class="headerlink"
href="#known-security-issues" title="Permanent link">¶</a></h2>
<p>Here is a list of known security issues with Apache VCL along with the
versions affected, versions
in which they were fixed, and information on patching vulnerable versions.</p>
-<h1 id="h3-cve-2018-11772">h3 CVE-2018-11772<a class="headerlink"
href="#h3-cve-2018-11772" title="Permanent link">¶</a></h1>
+<h3 id="cve-2018-11772">CVE-2018-11772<a class="headerlink"
href="#cve-2018-11772" title="Permanent link">¶</a></h3>
<ul>
<li>Announced: July 29th, 2019</li>
<li>Affected versions: versions 2.1 through 2.5</li>
@@ -131,7 +131,7 @@ However, all VCL systems running version
This vulnerability was found and reported to the Apache VCL project by ADLab
of Venustech.</p>
</li>
</ul>
-<h1 id="h3-cve-2018-11773">h3 CVE-2018-11773<a class="headerlink"
href="#h3-cve-2018-11773" title="Permanent link">¶</a></h1>
+<h3 id="cve-2018-11773">CVE-2018-11773<a class="headerlink"
href="#cve-2018-11773" title="Permanent link">¶</a></h3>
<ul>
<li>Announced: July 29th, 2019</li>
<li>Affected versions: versions 2.1 through 2.5</li>
@@ -149,7 +149,7 @@ should be upgraded or patched. This vuln
project by ADLab of Venustech.</p>
</li>
</ul>
-<h1 id="h3-cve-2018-11774">h3 CVE-2018-11774<a class="headerlink"
href="#h3-cve-2018-11774" title="Permanent link">¶</a></h1>
+<h3 id="cve-2018-11774">CVE-2018-11774<a class="headerlink"
href="#cve-2018-11774" title="Permanent link">¶</a></h3>
<ul>
<li>Announced: July 29th, 2019</li>
<li>Affected versions: versions 2.1 through 2.5</li>
@@ -166,7 +166,7 @@ running versions earlier than 2.5.1 shou
found and reported to the Apache VCL project by ADLab of Venustech.</p>
</li>
</ul>
-<h1 id="h3-cve-2013-0267">h3 CVE-2013-0267<a class="headerlink"
href="#h3-cve-2013-0267" title="Permanent link">¶</a></h1>
+<h3 id="cve-2013-0267">CVE-2013-0267<a class="headerlink"
href="#cve-2013-0267" title="Permanent link">¶</a></h3>
<ul>
<li>Announced: May 6th, 2013</li>
<li>Affected versions: versions 2.1, 2.2, 2.2.1, 2.3, 2.3.1</li>
