[JBoss JIRA] (WFCORE-4956) CVE-2020-10718 wildfly: exposed setting of TCCL via the EmbeddedManagedProcess API
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-4956?page=com.atlassian.jira.plug... ]
Brian Stansberry updated WFCORE-4956:
-------------------------------------
Summary: CVE-2020-10718 wildfly: exposed setting of TCCL via the EmbeddedManagedProcess API (was: EMBARGOED CVE-2020-10718 wildfly: exposed setting of TCCL via the EmbeddedManagedProcess API [eap-7.3.z])
> CVE-2020-10718 wildfly: exposed setting of TCCL via the EmbeddedManagedProcess API
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4956
> URL: https://issues.redhat.com/browse/WFCORE-4956
> Project: WildFly Core
> Issue Type: Bug
> Components: Embedded
> Reporter: Kunjan Rathod
> Assignee: James Perkins
> Priority: Minor
> Labels: CVE-2020-10718, Security, SecurityTracking, downstream_dependency, pscomponent:wildfly
> Fix For: 13.0.0.Beta5
>
>
> Security Tracking Issue
> Do not make this issue public.
> Impact: Low
> Public Date: not set
> Resolve Bug By: 545 calendar days from the public date
> In case the dates above are already past, please evaluate this bug in your next prioritization review and make a decision then. Remember to explicitly set CLOSED:WONTFIX if you decide not to fix this bug.
> Please see the Security Errata Policy for further details: https://docs.engineering.redhat.com/x/9RBqB
> NOTE THIS ISSUE IS CURRENTLY EMBARGOED, DO NOT MAKE PUBLIC COMMITS OR COMMENTS ABOUT THIS ISSUE.
> Flaw:
> -----
> EMBARGOED CVE-2020-10718 wildfly: exposed setting of TCCL via the EmbeddedManagedProcess API
> https://bugzilla.redhat.com/show_bug.cgi?id=1828476
> The embedded managed process API has two methods exposed as public methods which can bypass the security manager.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFCORE-5147) Add TRACE / DEBUG logging for git integration
by Darran Lofthouse (Jira)
Darran Lofthouse created WFCORE-5147:
----------------------------------------
Summary: Add TRACE / DEBUG logging for git integration
Key: WFCORE-5147
URL: https://issues.redhat.com/browse/WFCORE-5147
Project: WildFly Core
Issue Type: Task
Components: Management
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 14.0.0.Beta1
The initial load can likely be at DEBUG level but ongoing persist calls should likely be at TRACE as they would be per model update.
Trying to debug some failures in the test case org.jboss.as.test.manualmode.management.persistence.RemoteSshGitRepositoryTestCase when executed using GitHub actions some messages from jgit seem missing but as there is no debug or trace logging around our use of jgit it is not clear if that logging is missing because jgit is not being called or if the messages are not getting flushed to the logs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFCORE-4486) Support for multiple security realms - Failover
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFCORE-4486?page=com.atlassian.jira.plug... ]
Jeff Mesnil updated WFCORE-4486:
--------------------------------
Fix Version/s: (was: 13.0.0.Final)
> Support for multiple security realms - Failover
> -----------------------------------------------
>
> Key: WFCORE-4486
> URL: https://issues.redhat.com/browse/WFCORE-4486
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Farah Juma
> Assignee: Martin Mazánek
> Priority: Major
> Labels: CD17-Deferred
> Fix For: 13.0.0.Beta5
>
>
> Our security realms are able to indicate unavailability by throwing a RealmUnavailableException
> We should support fail over to an alternative realm.
> A common request is fail over to a local file based realm if an LDAP or database server has gone down allowing administrators to retain access to the server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months