Bug 1498378 (CVE-2017-12174)
| Summary: | CVE-2017-12174 artemis/hornetq: memory exhaustion via UDP and JGroups discovery | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Bharti Kundal <bkundal> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | aboyko, apintea, asoldano, atangrin, bbaranow, bkundal, bmaxwell, brian.stansberry, cdewolf, chazlett, csutherl, darran.lofthouse, dimitris, dkreling, dosoudil, fgavrilo, iweiss, jawilson, jochrist, jondruse, jperkins, jshepherd, jwon, kconner, krathod, kwills, lgao, loleary, mnovak, msochure, msvehla, myarboro, nwallace, pgier, pjindal, pjurak, pmackay, ppalaga, psakar, psampaio, pslavice, psotirop, rguimara, rnetuka, rstancel, rsvoboda, security-response-team, smaestri, spinder, theute, tom.jenkinson, twalsh, vtunka |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: |
It was found that when Artemis and HornetQ are configured with UDP discovery and JGroups discovery a huge byte array is created when receiving an unexpected multicast message. This may result in a heap memory exhaustion, full GC, or OutOfMemoryError.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-07 19:51:06 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1498776, 1498777 | ||
| Bug Blocks: | 1494635, 1537472 | ||
|
Description
Bharti Kundal
2017-10-04 07:32:54 UTC
Acknowledgments: Name: Masafumi Miura (Red Hat) This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform Via RHSA-2018:0269 https://access.redhat.com/errata/RHSA-2018:0269 This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 7 Via RHSA-2018:0268 https://access.redhat.com/errata/RHSA-2018:0268 This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 5 Via RHSA-2018:0271 https://access.redhat.com/errata/RHSA-2018:0271 This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Via RHSA-2018:0270 https://access.redhat.com/errata/RHSA-2018:0270 This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Via RHSA-2018:0275 https://access.redhat.com/errata/RHSA-2018:0275 This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform Via RHSA-2018:0478 https://access.redhat.com/errata/RHSA-2018:0478 This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.1 for RHEL 7 Via RHSA-2018:0480 https://access.redhat.com/errata/RHSA-2018:0480 This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.1 for RHEL 6 Via RHSA-2018:0479 https://access.redhat.com/errata/RHSA-2018:0479 This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.1 for RHEL 7 Red Hat JBoss Enterprise Application Platform 7.1 for RHEL 6 Via RHSA-2018:0481 https://access.redhat.com/errata/RHSA-2018:0481 This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform Via RHSA-2020:2561 https://access.redhat.com/errata/RHSA-2020:2561 |