<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Postgres CVE-2020-13692 in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Postgres-CVE-2020-13692/m-p/695895#M20586</link>
    <description>&lt;P&gt;Good day.&lt;/P&gt;&lt;P&gt;I got a question concerning the following.&lt;/P&gt;&lt;P&gt;Is&amp;nbsp; SAS 9.4 vulnerable for the following postgres flaw ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Description of problem:&lt;/P&gt;&lt;P&gt;An XML eXternal Entity (XXE) flaw was discovered in the PgSQLXML implementation that is known as CVE-2020-13692. This flaw could possibly allow disclosure of confidential data (such as content of local files), denial of service, server side request forgery (SSRF), or other impacts, if specially crafted XML documents are processed by PgSQLXML.&lt;/P&gt;&lt;P&gt;In order to fix the CVE-2020-13692 issue, the PgSQLXML implementation in postgresql-jdbc was modified to disable loading of external entities and document type definitions (DTD) by default. &lt;STRONG&gt;This change may introduce a regression in environments that rely on processing of external entities or DTDs.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For environments that require processing of external entities or DTDs, it is possible to configured PgSQLXML to use the previous behaviour and perform loading of external objects. This legacy behaviour can be enabled for each database connection by setting the xmlFactoryFactory property to the value of LEGACY_INSECURE.&lt;/P&gt;&lt;P&gt;Note: &lt;STRONG&gt;This setting enables processing of external entities and DTDs and therefore re-introduces the CVE-2020-13692 issue.&lt;/STRONG&gt; It should only be used when XML documents stored in a database and processed using the PgSQLXML are fully trusted.&lt;/P&gt;</description>
    <pubDate>Mon, 02 Nov 2020 11:04:12 GMT</pubDate>
    <dc:creator>paterd2</dc:creator>
    <dc:date>2020-11-02T11:04:12Z</dc:date>
    <item>
      <title>Postgres CVE-2020-13692</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Postgres-CVE-2020-13692/m-p/695895#M20586</link>
      <description>&lt;P&gt;Good day.&lt;/P&gt;&lt;P&gt;I got a question concerning the following.&lt;/P&gt;&lt;P&gt;Is&amp;nbsp; SAS 9.4 vulnerable for the following postgres flaw ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Description of problem:&lt;/P&gt;&lt;P&gt;An XML eXternal Entity (XXE) flaw was discovered in the PgSQLXML implementation that is known as CVE-2020-13692. This flaw could possibly allow disclosure of confidential data (such as content of local files), denial of service, server side request forgery (SSRF), or other impacts, if specially crafted XML documents are processed by PgSQLXML.&lt;/P&gt;&lt;P&gt;In order to fix the CVE-2020-13692 issue, the PgSQLXML implementation in postgresql-jdbc was modified to disable loading of external entities and document type definitions (DTD) by default. &lt;STRONG&gt;This change may introduce a regression in environments that rely on processing of external entities or DTDs.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For environments that require processing of external entities or DTDs, it is possible to configured PgSQLXML to use the previous behaviour and perform loading of external objects. This legacy behaviour can be enabled for each database connection by setting the xmlFactoryFactory property to the value of LEGACY_INSECURE.&lt;/P&gt;&lt;P&gt;Note: &lt;STRONG&gt;This setting enables processing of external entities and DTDs and therefore re-introduces the CVE-2020-13692 issue.&lt;/STRONG&gt; It should only be used when XML documents stored in a database and processed using the PgSQLXML are fully trusted.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Nov 2020 11:04:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Postgres-CVE-2020-13692/m-p/695895#M20586</guid>
      <dc:creator>paterd2</dc:creator>
      <dc:date>2020-11-02T11:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: Postgres CVE-2020-13692</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Postgres-CVE-2020-13692/m-p/696065#M20600</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/223604"&gt;@paterd2&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can find the security bulletins and vulnerabilities related information from SAS at this site:&amp;nbsp;&lt;A href="https://support.sas.com/en/security-bulletins.html#security-bulletins" target="_blank" rel="noopener"&gt;https://support.sas.com/en/security-bulletins.html#security-bulletins&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;I don't see the postgres one listed. I would suggest you to raise a technical support track to get it confirmed. You can raise a track by emailing the details to &lt;A href="mailto:support@sas.com" target="_blank" rel="noopener"&gt;support@sas.com&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Nov 2020 01:05:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Postgres-CVE-2020-13692/m-p/696065#M20600</guid>
      <dc:creator>AnandVyas</dc:creator>
      <dc:date>2020-11-03T01:05:20Z</dc:date>
    </item>
  </channel>
</rss>

