<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>openssl on Rich Mirch</title>
    <link>https://blog.mirch.io/tags/openssl/</link>
    <description>Recent content in openssl on Rich Mirch</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 10 Jun 2019 12:13:44 +0000</lastBuildDate>
    <atom:link href="https://blog.mirch.io/tags/openssl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CVE-2019-12572 PIA Windows Privilege Escalation: Malicious OpenSSL Engine</title>
      <link>https://blog.mirch.io/2019/06/10/cve-2019-12572-pia-windows-privilege-escalation-malicious-openssl-engine/</link>
      <pubDate>Mon, 10 Jun 2019 12:13:44 +0000</pubDate>
      <guid>https://blog.mirch.io/2019/06/10/cve-2019-12572-pia-windows-privilege-escalation-malicious-openssl-engine/</guid>
      <description>&lt;h2 id=&#34;vulnerability-summary&#34;&gt;&lt;strong&gt;Vulnerability Summary&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;During startup the PIA Windows service(pia-service.exe) loads the OpenSSL library from C:\Program Files\Private Internet Access\libeay32.dll. This library attempts to load the C:\etc\ssl\openssl.cnf configuration file. By default on Windows systems, authenticated users can create directories under C:\. A low privileged user can create an openssl.cnf configuration file to load a malicious OpenSSL engine library resulting in arbitrary code execution as SYSTEM when the service starts.&lt;/p&gt;
&lt;p&gt;The root cause is when the OpenSSL libraries were built, the &lt;a href=&#34;https://wiki.openssl.org/index.php/Compilation_and_Installation#PREFIX_and_OPENSSLDIR&#34;&gt;OPENSSLDIR&lt;/a&gt; parameter was set to a path which a low privileged user can modify or create. I believe this issue is lurking in many Windows applications that bundle OpenSSL libraries. I have discovered the same vulnerability in several other Windows applications and will be disclosing those findings when patches are available.&lt;/p&gt;
&lt;p&gt;I created a simple tool to help identify potentially vulnerable OpenSSL libraries - &lt;a href=&#34;https://github.com/mirchr/openssldir_check&#34;&gt;https://github.com/mirchr/openssldir_check&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;CVE-2019-12572 has been patched in v1.2.1. The latest Windows desktop client can be upgraded automatically via the application or manually from the download page at &lt;a href=&#34;https://www.privateinternetaccess.com/pages/download&#34;&gt;Private Internet Access&lt;/a&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;walkthrough&#34;&gt;&lt;strong&gt;Walkthrough&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;While hunting for potential vulnerabilities in the Windows Private Internet Access desktop application I noticed a failed call to open the c:\etc\ssl\openssl.cnf file during the service startup.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&#34;pia-openssl-failed-open&#34; loading=&#34;lazy&#34; src=&#34;https://blog.mirch.io/images/2019/06/pia-openssl-failed-open.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;This caught my attention and I needed to research this further. But before I get into the details of that, let&amp;rsquo;s take a step back and see how I arrived there.&lt;/p&gt;
</description>
    </item>
  </channel>
</rss>
