REDHAT-BUG-487685: Medium severity Apache Camel vulnerability
It was discovered that camel's NTLM SASL authentication mechanism did not properly validate server's challenge packets (NTLM authentication type 2 packets, [1]). In the ntlmchallenge() in camel/camel-sasl-ntlm.c, length of the domain string that was copied from type 2 to type 3 packet (client's reply to server's challenge) was not properly validated against the rest of the data received from the server.
127 ntlmsetstring (ret, NTLMRESPONSEDOMAINOFFSET, 128 token->data + NTLMCHALLENGEDOMAINOFFSET, 129 atoi (token->data + NTLMCHALLENGEDOMAINLENOFFSET));
Server could specify larger length than the actual data sent in the packet, causing the client to disclose portion of its memory, or crash.
Note: length value was not properly extracted from the packet too, as it is not passed as string, rather as 16-bit LE value.
[1] http://curl.haxx.se/rfc/ntlm.html#theType2Message
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-487685?
The severity of REDHAT-BUG-487685 is considered critical due to the improper validation of NTLM SASL authentication challenge packets.
How do I fix REDHAT-BUG-487685?
To fix REDHAT-BUG-487685, update Apache Camel to the latest version that addresses this vulnerability.
What systems are affected by REDHAT-BUG-487685?
REDHAT-BUG-487685 affects systems using the Apache Camel NTLM SASL authentication mechanism.
What type of vulnerability is REDHAT-BUG-487685?
REDHAT-BUG-487685 is an authentication vulnerability related to improper validation of challenge packets.
Is REDHAT-BUG-487685 exploitable remotely?
Yes, REDHAT-BUG-487685 is potentially exploitable remotely due to the nature of the NTLM authentication process.