Bug 1921126 (CVE-2021-26117) - CVE-2021-26117 activemq: LDAP authentication bypass with anonymous bind
Summary: CVE-2021-26117 activemq: LDAP authentication bypass with anonymous bind
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2021-26117
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1880635
TreeView+ depends on / blocked
 
Reported: 2021-01-27 14:54 UTC by Jonathan Christison
Modified: 2021-02-16 17:13 UTC (History)
11 users (show)

Fixed In Version: activemq-artemis-2.16.0 redhat-amq-7.8.0 redhat-amq-7.4.5
Clone Of:
Environment:
Last Closed: 2021-02-02 14:42:22 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:0384 0 None None None 2021-02-02 14:23:36 UTC

Description Jonathan Christison 2021-01-27 14:54:13 UTC
A flaw was found in Red Hat AMQ 6 and ActiveMQ Artemis (Red Hat AMQ 7) with the LDAP login module, if anonymous binds are enabled on the LDAP provider (zero length DN/password) and the LDAP module is configured to make use of these, client credentials are not correctly verified and authentication is effectively bypassed. 

Upstream Issue: https://issues.apache.org/jira/browse/ARTEMIS-2895

Comment 3 Pedro Sampaio 2021-01-27 21:25:15 UTC
Public: https://www.openwall.com/lists/oss-security/2021/01/27/6

Comment 6 Chess Hazlett 2021-01-29 20:02:42 UTC
Mitigation:

There is currently no known mitigation for this issue.

Comment 7 errata-xmlrpc 2021-02-02 14:23:34 UTC
This issue has been addressed in the following products:

  Red Hat Fuse/AMQ 6.3.18

Via RHSA-2021:0384 https://access.redhat.com/errata/RHSA-2021:0384

Comment 8 Product Security DevOps Team 2021-02-02 14:42:22 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2021-26117


Note You need to log in before you can comment on or make changes to this bug.