January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (SSLNTV-11) Add a new GitHub workflow to trigger native builds for pull requests and tags

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/SSLNTV-11?page=com.atlassian.jira.plugin... ] Farah Juma updated SSLNTV-11: ----------------------------- Summary: Add a new GitHub workflow to trigger native builds for pull requests and tags (was: Add a new GitHub workflow to trigger CI for pull requests and tags) > Add a new GitHub workflow to trigger native builds for pull requests and tags > ----------------------------------------------------------------------------- > > Key: SSLNTV-11 > URL: https://issues.redhat.com/browse/SSLNTV-11 > Project: WildFly OpenSSL Natives > Issue Type: Enhancement > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14189) The RunAs annotation doesn't work in EJBs with Elytron

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14189?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14189: ------------------------------------ Component/s: EJB > The RunAs annotation doesn't work in EJBs with Elytron > ------------------------------------------------------ > > Key: WFLY-14189 > URL: https://issues.redhat.com/browse/WFLY-14189 > Project: WildFly > Issue Type: Bug > Components: EJB, Security > Affects Versions: 21.0.0.Final > Reporter: Alessandro Moscatelli > Priority: Major > Labels: ejb, elytron, regression, runas, security, startup > Attachments: standalone-full-ha.new.xml, test.zip > > > Role is not correctly assigned when using @RunAs annotation and Elytron Security Domain. Everything works correctly with legacy picketbox Security Domain. > Wildfly is configured to use default "other" application-security-domain, also using default security domain ApplicationDomain. > This exception is rised when deploying the application. > Caused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowedCaused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowed at org.jboss.as.ejb3@21.0.0.Final//org.jboss.as.ejb3.security.JaccInterceptor.hasPermission(JaccInterceptor.java:120) > Test/Sample project: [^test.zip] -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14260) ClassCastException during expiration scheduling

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-14260: ----------------------------------- Summary: ClassCastException during expiration scheduling Key: WFLY-14260 URL: https://issues.redhat.com/browse/WFLY-14260 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 22.0.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro This appears to be a regression due to: https://github.com/wildfly/wildfly/commit/ff22a98553a4168a9cd47a8fbf59afa... As seen on CI: {noformat} [0m09:30:39,897 INFO [org.wildfly.clustering.ee.infinispan] (default task-2) WFLYCLEEINF0002: Failed to schedule 3wnQESQq-yAwHD6_ygq39emcPLeSonW6P-oDO-0N on primary owner.: java.lang.ClassCastException: org.infinispan.remoting.transport.jgroups.JGroupsAddress cannot be cast to org.jgroups.Address at org.wildfly.clustering.server.dispatcher.ChannelCommandDispatcherFactory.createNode(ChannelCommandDispatcherFactory.java:98) at org.wildfly.clustering.ee.infinispan.PrimaryOwnerLocator.apply(PrimaryOwnerLocator.java:57) at org.wildfly.clustering.ee.infinispan.PrimaryOwnerLocator.apply(PrimaryOwnerLocator.java:39) at org.wildfly.clustering.ee.infinispan.scheduler.PrimaryOwnerScheduler$1.get(PrimaryOwnerScheduler.java:81) at org.wildfly.clustering.ee.infinispan.scheduler.PrimaryOwnerScheduler$1.get(PrimaryOwnerScheduler.java:78) at org.wildfly.clustering.ee.cache.retry.RetryingInvoker.invoke(RetryingInvoker.java:72) at org.wildfly.clustering.ee.infinispan.scheduler.PrimaryOwnerScheduler.executeOnPrimaryOwner(PrimaryOwnerScheduler.java:86) at org.wildfly.clustering.ee.infinispan.scheduler.PrimaryOwnerScheduler.schedule(PrimaryOwnerScheduler.java:59) at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$1.accept(InfinispanSessionManager.java:123) at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$1.accept(InfinispanSessionManager.java:119) at org.wildfly.clustering.web.cache.session.ValidSession.close(ValidSession.java:89) at org.wildfly.clustering.web.cache.session.ConcurrentSessionManager$ConcurrentSession.closeSession(ConcurrentSessionManager.java:151) at org.wildfly.clustering.web.cache.session.ConcurrentSessionManager$1.accept(ConcurrentSessionManager.java:55) at org.wildfly.clustering.web.cache.session.ConcurrentSessionManager$1.accept(ConcurrentSessionManager.java:52) at org.wildfly.clustering.ee.cache.SimpleManager$1.run(SimpleManager.java:55) at org.wildfly.clustering.web.cache.session.ConcurrentSessionManager$ConcurrentSession.close(ConcurrentSessionManager.java:182) at org.wildfly.clustering.web.undertow.session.DistributableSession.requestDone(DistributableSession.java:98) at io.undertow.servlet.spec.ServletContextImpl.updateSessionAccessTime(ServletContextImpl.java:960) at io.undertow.servlet.spec.HttpServletResponseImpl.responseDone(HttpServletResponseImpl.java:590) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:328) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:78) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:133) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:130) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:249) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:78) at io.undertow.servlet.handlers.ServletInitialHandler$1$1.run(ServletInitialHandler.java:105) at java.security.AccessController.doPrivileged(Native Method) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:102) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:387) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:841) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at org.xnio.XnioWorker$WorkerThreadFactory$1$1.run(XnioWorker.java:1280) at java.lang.Thread.run(Thread.java:748) {noformat} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2065) No suitable provider found for type 'PKCS11' on openjdk 11 when configuration is passed in provider-loader

by Diana Vilkolakova (Jira)

[ https://issues.redhat.com/browse/ELY-2065?page=com.atlassian.jira.plugin.... ] Diana Vilkolakova updated ELY-2065: ----------------------------------- Description: Steps to Reproduce work using OpenJDK 8, but on OpenJDK 11 the following exception gets thrown: {code} {{ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([}} {{ ("subsystem" => "elytron"),}} {{ ("key-store" => "pkcs11ks")}} {{]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.pkcs11ks" => "WFLYELY00004: Unable to start the service.}} {{ Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYELY00012: No suitable provider found for type 'PKCS11'"}}}} {code} Configuration loading for SunPKCS11 was changed after Java 8 and the constructor that accepts InputStream configuration is not present in openjdk 11. Maybe because of this, the configuration is ignored when it is passed in *provider-loader*. was: Steps to Reproduce work using OpenJDK 8, but on OpenJDK 11 the following exception gets thrown: {{ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([}} {{ ("subsystem" => "elytron"),}} {{ ("key-store" => "pkcs11ks")}} {{]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.pkcs11ks" => "WFLYELY00004: Unable to start the service.}} {{ Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYELY00012: No suitable provider found for type 'PKCS11'"}}}} Configuration loading for SunPKCS11 was changed after Java 8 and the constructor that accepts InputStream configuration is not present in openjdk 11. Maybe because of this, the configuration is ignored when it is passed in *provider-loader*. > No suitable provider found for type 'PKCS11' on openjdk 11 when configuration is passed in provider-loader > ---------------------------------------------------------------------------------------------------------- > > Key: ELY-2065 > URL: https://issues.redhat.com/browse/ELY-2065 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > > Steps to Reproduce work using OpenJDK 8, but on OpenJDK 11 the following exception gets thrown: > {code} > {{ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([}} > {{ ("subsystem" => "elytron"),}} > {{ ("key-store" => "pkcs11ks")}} > {{]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.pkcs11ks" => "WFLYELY00004: Unable to start the service.}} > {{ Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYELY00012: No suitable provider found for type 'PKCS11'"}}}} > {code} > Configuration loading for SunPKCS11 was changed after Java 8 and the constructor that accepts InputStream configuration is not present in openjdk 11. Maybe because of this, the configuration is ignored when it is passed in *provider-loader*. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2065) No suitable provider found for type 'PKCS11' on openjdk 11 when configuration is passed in provider-loader

by Diana Vilkolakova (Jira)

[ https://issues.redhat.com/browse/ELY-2065?page=com.atlassian.jira.plugin.... ] Diana Vilkolakova updated ELY-2065: ----------------------------------- Steps to Reproduce: The below steps will pass using OpenJDK 8, but will throw an exception using OpenJDK 11. 1. Configure NSS: {code} mkdir /tmp/nssdb echo "pass123+" > /tmp/newpass.txt echo "dsadasdasdasdadasdasdasdasdsadfwerwerjfdksdjfksdlfhjsdk" > /tmp/noise.txt MODUTIL_CMD="modutil -force -dbdir /tmp/nssdb"$MODUTIL_CMD -create $MODUTIL_CMD -changepw "NSS Certificate DB" -newpwfile /tmp/newpass.txt certutil -S -v 240 -k rsa -n "CN=localhost" -t "u,u,u" -x -s "CN=localhost" -d /tmp/nssdb -f /tmp/newpass.txt -z /tmp/noise.txt touch /tmp/nssdb/secmod.db $JBOSS_HOME/bin/standalone.sh $JBOSS_HOME/bin/jboss-cli -c {code} 2. Configure keystore: {code} /subsystem=elytron/provider-loader=nss:add(class-names=["sun.security.pkcs11.SunPKCS11"], configuration=\{name=testPkcs11, nssLibraryDirectory=/usr/lib64, nssSecmodDirectory=/tmp/nssdb, nssModule=keystore, name=testPkcs11},module=sun.jdk) /subsystem=elytron/key-store=pkcs11ks:add(credential-reference=\{clear-text=pass123+}, type=PKCS11, providers=nss) {code} was: The below steps will pass using OpenJDK 8, but will throw an exception using OpenJDK 11. 1. Configure NSS: mkdir /tmp/nssdb echo "pass123+" > /tmp/newpass.txt echo "dsadasdasdasdadasdasdasdasdsadfwerwerjfdksdjfksdlfhjsdk" > /tmp/noise.txt MODUTIL_CMD="modutil -force -dbdir /tmp/nssdb"$MODUTIL_CMD -create $MODUTIL_CMD -changepw "NSS Certificate DB" -newpwfile /tmp/newpass.txt certutil -S -v 240 -k rsa -n "CN=localhost" -t "u,u,u" -x -s "CN=localhost" -d /tmp/nssdb -f /tmp/newpass.txt -z /tmp/noise.txt touch /tmp/nssdb/secmod.db $JBOSS_HOME/bin/standalone.sh $JBOSS_HOME/bin/jboss-cli -c 2. Configure keystore: /subsystem=elytron/provider-loader=nss:add(class-names=["sun.security.pkcs11.SunPKCS11"], configuration=\{name=testPkcs11, nssLibraryDirectory=/usr/lib64, nssSecmodDirectory=/tmp/nssdb, nssModule=keystore, name=testPkcs11},module=sun.jdk)/subsystem=elytron/key-store=pkcs11ks:add(credential-reference=\{clear-text=pass123+}, type=PKCS11, providers=nss) > No suitable provider found for type 'PKCS11' on openjdk 11 when configuration is passed in provider-loader > ---------------------------------------------------------------------------------------------------------- > > Key: ELY-2065 > URL: https://issues.redhat.com/browse/ELY-2065 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > > > Steps to Reproduce work using OpenJDK 8, but on OpenJDK 11 the following exception gets thrown: > {{ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([}} > {{ ("subsystem" => "elytron"),}} > {{ ("key-store" => "pkcs11ks")}} > {{]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.pkcs11ks" => "WFLYELY00004: Unable to start the service.}} > {{ Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYELY00012: No suitable provider found for type 'PKCS11'"}}}} > Configuration loading for SunPKCS11 was changed after Java 8 and the constructor that accepts InputStream configuration is not present in openjdk 11. Maybe because of this, the configuration is ignored when it is passed in *provider-loader*. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (SSLNTV-11) Add a new GitHub workflow to trigger CI for pull requests and tags

by Farah Juma (Jira)

Farah Juma created SSLNTV-11: -------------------------------- Summary: Add a new GitHub workflow to trigger CI for pull requests and tags Key: SSLNTV-11 URL: https://issues.redhat.com/browse/SSLNTV-11 Project: WildFly OpenSSL Natives Issue Type: Enhancement Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2065) No suitable provider found for type 'PKCS11' on openjdk 11 when configuration is passed in provider-loader

by Diana Vilkolakova (Jira)

Diana Vilkolakova created ELY-2065: -------------------------------------- Summary: No suitable provider found for type 'PKCS11' on openjdk 11 when configuration is passed in provider-loader Key: ELY-2065 URL: https://issues.redhat.com/browse/ELY-2065 Project: WildFly Elytron Issue Type: Bug Components: API / SPI Reporter: Diana Vilkolakova Assignee: Diana Vilkolakova Steps to Reproduce work using OpenJDK 8, but on OpenJDK 11 the following exception gets thrown: {{ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([}} {{ ("subsystem" => "elytron"),}} {{ ("key-store" => "pkcs11ks")}} {{]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.pkcs11ks" => "WFLYELY00004: Unable to start the service.}} {{ Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYELY00012: No suitable provider found for type 'PKCS11'"}}}} Configuration loading for SunPKCS11 was changed after Java 8 and the constructor that accepts InputStream configuration is not present in openjdk 11. Maybe because of this, the configuration is ignored when it is passed in *provider-loader*. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14142) Upgrade Google guava from 25.0-jre to 30.1-jre (addresses CVE-2020-8908)

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14142?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14142: ------------------------------------ Summary: Upgrade Google guava from 25.0-jre to 30.1-jre (addresses CVE-2020-8908) (was: Upgrade Google guava from 25.0-jre to 30.1-jre) > Upgrade Google guava from 25.0-jre to 30.1-jre (addresses CVE-2020-8908) > ------------------------------------------------------------------------ > > Key: WFLY-14142 > URL: https://issues.redhat.com/browse/WFLY-14142 > Project: WildFly > Issue Type: Component Upgrade > Components: Batch, JMS, Test Suite > Reporter: Boris Unckel > Assignee: Cheng Fang > Priority: Major > Attachments: 2020-12-01_04after_guava_build.txt, WFCORE5203_WFLY14142_test_analysis.7z > > > Update Google guava to [30.1-jre|https://mvnrepository.com/artifact/com.google.guava/guava/30.1-jre]. Exclude all dependencies but [failureaccess 1.0.1|https://mvnrepository.com/artifact/com.google.guava/failureaccess/1...] according to [Google Guava Important Warnings #3|https://github.com/google/guava]. > [Release Notes|https://github.com/google/guava/releases/tag/v30.1] > [Release-Diff|https://github.com/google/guava/compare/v25.0...v30.1] > The update is justified due to ForkJoin Security Manager improvement: [Issue 3784|https://github.com/google/guava/issues/3784] [Commit|https://github.com/google/guava/commit/6e0c5b5d50a3e457ae0d787f7c9...] -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14247) Error Page is not displayed when trying to access META-INF or WEB-INF

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14247?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-14247: --------------------------------------- Component/s: Web (Undertow) Assignee: Flavia Rainone (was: Brian Stansberry) > Error Page is not displayed when trying to access META-INF or WEB-INF > --------------------------------------------------------------------- > > Key: WFLY-14247 > URL: https://issues.redhat.com/browse/WFLY-14247 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 21.0.2.Final > Reporter: Melvin Yam > Assignee: Flavia Rainone > Priority: Minor > Attachments: mywebapp.war > > > I have a simple webapp war file with the following structure: > {quote}{{Listing archive: mywebapp.war}}{{--}} > {{Path = mywebapp.war}} > {{Type = zip}} > {{Physical Size = 1441}}{{Date Time Attr Size Compressed Name}} > {{------------------- ----- ------------ ------------ ------------------------}} > {{2020-12-23 20:09:20 ....A 18 18 error.html}} > {{2020-12-23 20:09:02 ....A 18 18 index.html}} > {{2020-12-23 20:10:13 D.... 0 0 META-INF}} > {{2020-12-23 03:16:37 ....A 39 39 META-INF\MANIFEST.MF}} > {{2020-12-23 20:12:38 D.... 0 0 WEB-INF}} > {{2020-12-23 20:12:28 D.... 0 0 WEB-INF\classes}} > {{2020-12-23 20:12:35 D.... 0 0 WEB-INF\lib}} > {{2020-12-23 20:11:54 ....A 480 248 WEB-INF\web.xml}} > {{------------------- ----- ------------ ------------ ------------------------}} > {{2020-12-23 20:12:38 555 323 4 files, 4 folders}} > {quote} > > In web.xml, it defines the error page: > {quote}<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.jcp.org/xml/ns/javaee" > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_4_0.xsd" version="4.0"> > <display-name>mywebapp</display-name> > <welcome-file-list> > <welcome-file>index.html</welcome-file> > </welcome-file-list> > <error-page> > <location>/error.html</location> > </error-page> > </web-app> > {quote} > > After deploying the webapp successfully in local WildFly server. > Accessing the following URL will trigger the error page to be shown: > [http://127.0.0.1:8080/mywebapp/dummy] > [http://127.0.0.1:8080/mywebapp/META-INF/MANIFEST.MF] > [http://127.0.0.1:8080/mywebapp/META-INF/dummy/dummy] > > However, the following URL will NOT trigger the error page: > [http://127.0.0.1:8080/mywebapp/META-INF] > [http://127.0.0.1:8080/mywebapp/WEB-INF] > [http://127.0.0.1:8080/mywebapp/WEB-INF/web.xml|http://127.0.0.1:8080/mywe...] > [http://127.0.0.1:8080/mywebapp/WEB-INF/dummy/dummy] > Instead, it just displays the text "404 - Not Found" > > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13468) Upgrade codehaus/jackson from 1.9.13.redhat-00006 to 1.9.13-redhat-00007 (resolves CVE-2019-10172)

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13468?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13468: ------------------------------------ Security: (was: Security Issue) > Upgrade codehaus/jackson from 1.9.13.redhat-00006 to 1.9.13-redhat-00007 (resolves CVE-2019-10172) > -------------------------------------------------------------------------------------------------- > > Key: WFLY-13468 > URL: https://issues.redhat.com/browse/WFLY-13468 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Bartosz Baranowski > Assignee: James Perkins > Priority: Blocker > Fix For: 20.0.0.Beta1, 20.0.0.Final > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021