[JBoss JIRA] (TEIID-5823) CVE's in jboss-fuse/teiid
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5823?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-5823:
-------------------------------
Description:
*Branch/Tag*: 12.3.1.fuse-750011-redhat-00001
* *Severity*: {color:#f9423a}High{color}
1. apache commons collections
* Vulnerability ID: CVE-2015-6420
2. org.apache.lucene:lucene-queryparser - Remote Code Execution (RCE)
* Vulnerability ID: CVE-2017-12629
3. org.slf4j:slf4j-ext - Access Restriction Bypass
* Vulnerability ID: CVE-2018-8088
These changes will be committed to the teiid/teiid product branch 7.5-12.3.x and to master.
was:
*Branch/Tag*: 12.3.1.fuse-750011-redhat-00001
* *Severity*: {color:#f9423a}High{color}
1. apache commons collections
* Vulnerability ID: CVE-2015-6420
2. org.apache.lucene:lucene-queryparser - Remote Code Execution (RCE)
* Vulnerability ID: CVE-2017-12629
3. org.slf4j:slf4j-ext - Access Restriction Bypass
* Vulnerability ID: CVE-2018-8088
> CVE's in jboss-fuse/teiid
> -------------------------
>
> Key: TEIID-5823
> URL: https://issues.jboss.org/browse/TEIID-5823
> Project: Teiid
> Issue Type: Quality Risk
> Components: Build/Kits
> Affects Versions: 13.x, 12.3.1
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Blocker
>
> *Branch/Tag*: 12.3.1.fuse-750011-redhat-00001
> * *Severity*: {color:#f9423a}High{color}
> 1. apache commons collections
> * Vulnerability ID: CVE-2015-6420
> 2. org.apache.lucene:lucene-queryparser - Remote Code Execution (RCE)
> * Vulnerability ID: CVE-2017-12629
> 3. org.slf4j:slf4j-ext - Access Restriction Bypass
> * Vulnerability ID: CVE-2018-8088
> These changes will be committed to the teiid/teiid product branch 7.5-12.3.x and to master.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (TEIID-5823) CVE's in jboss-fuse/teiid
by Van Halbert (Jira)
[ https://issues.jboss.org/browse/TEIID-5823?page=com.atlassian.jira.plugin... ]
Van Halbert moved ENTESB-11967 to TEIID-5823:
---------------------------------------------
Project: Teiid (was: Red Hat Fuse)
Key: TEIID-5823 (was: ENTESB-11967)
Issue Type: Quality Risk (was: Bug)
Workflow: classic default workflow (was: ENTESB Triaged Work)
Component/s: Build/Kits
(was: Data Integration)
Affects Version/s: 13.x
12.3.1
(was: fuse-7.5-ER1)
> CVE's in jboss-fuse/teiid
> -------------------------
>
> Key: TEIID-5823
> URL: https://issues.jboss.org/browse/TEIID-5823
> Project: Teiid
> Issue Type: Quality Risk
> Components: Build/Kits
> Affects Versions: 13.x, 12.3.1
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Blocker
>
> *Branch/Tag*: 12.3.1.fuse-750011-redhat-00001
> * *Severity*: {color:#f9423a}High{color}
> 1. apache commons collections
> * Vulnerability ID: CVE-2015-6420
> 2. org.apache.lucene:lucene-queryparser - Remote Code Execution (RCE)
> * Vulnerability ID: CVE-2017-12629
> 3. org.slf4j:slf4j-ext - Access Restriction Bypass
> * Vulnerability ID: CVE-2018-8088
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (TEIID-5557) Restrict imports to a single schema
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5557?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5557.
-----------------------------------
Resolution: Done
The default for useFullSchemaName is now false and to import from multiple foreign schema you generally need to set useFullSchemaName to true. There's a env/system property for backwards compatibility, but in general this will force people to set the schemaName or schemaPattern.
> Restrict imports to a single schema
> -----------------------------------
>
> Key: TEIID-5557
> URL: https://issues.jboss.org/browse/TEIID-5557
> Project: Teiid
> Issue Type: Quality Risk
> Components: Connector API
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0
>
>
> To better align with SQL/MED and to simplify legacy import properties it would be best to restrict foreign imports to a single schema. This will remove quite a bit of confusion around potential duplicate object names.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months