0day.today - Biggest Exploit Database in the World.
- We use one main domain: http://0day.today
- Most of the materials is completely FREE
- If you want to purchase the exploit / get V.I.P. access or pay for any other service,
you need to buy or earn
GOLD
Administration of this site uses the official contacts. Beware of impostors!
We DO NOT use Telegram or any messengers / social networks!Please, beware of scammers!
- Read the [ agreement ]
- Read the [ Submit ] rules
- Visit the [ faq ] page
- [ Register ] profile
- Get [ GOLD ]
- If you want to [ sell ]
- If you want to [ buy ]
- If you lost [ Account ]
- Any questions [ admin@0day.today ]
- Authorisation page
- Registration page
- Restore account page
- FAQ page
- Contacts page
- Publishing rules
- Agreement page
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
Contact us
You can contact us by:
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
Apache Qpid Broker For Java 6.1.0 Information Leak Vulnerability
Author
Risk
[Security Risk High
]0day-ID
Category
Date add
CVE
Platform
[CVE-2016-8741] Apache Qpid Broker for Java - Information Leakage
Vendor: The Apache Software Foundation
Versions Affected: Apache Qpid Broker for Java versions 6.0.1,
6.0.2, 6.0.3, 6.0.4, 6.0.5, and 6.1.0
Description:
The Qpid Broker for Java can be configured to use different so
called AuthenticationProviders to handle user authentication.
Among the choices are the SCRAM-SHA-1 and SCRAM-SHA-256
AuthenticationProvider types.
It was discovered that these AuthenticationProviders prematurely
terminate the SCRAM SASL negotiation if the provided user name
does not exist thus allowing remote attacker to determine the
existence of user accounts.
The Vulnerability does not apply to AuthenticationProviders other
than SCRAM-SHA-1 and SCRAM-SHA-256.
Resolution:
Users should upgrade the Qpid Broker for Java to version 6.0.6,
6.1.1, or later (recommended).
Mitigation:
If upgrading is not possible, the vulnerability can be mitigated
by using an AuthenticationProvider other than SCRAM-SHA-1 and
SCRAM-SHA-256.
References:
https://issues.apache.org/jira/browse/QPID-7599
# 0day.today [2024-11-15] #