Pam self hosted mitigating radius vulnerability (CVE-2024-3596)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Pam self hosted mitigating radius vulnerability (CVE-2024-3596)

L1 Bithead

 I was looking for some guidance in upgrading our cyberark installment to one that would be compatible with the new Radius CVE(CVE-2024-3596). All could find on the cyberark support site(https://community.cyberark.com/s/article/What-is-the-impact-of-RADIUS-Protocol-Vulnerability-CVE-202...) was a mention of it but nothing else?

 

I ask because I need to upgrade our radius server and the latest version has fixes for the radius vulnerability and so I would like to make sure that Cyberark will continue to function with radius authentication.

 

We are currently on version 12.6.11

6 REPLIES 6

L5 Sessionator

Yes it should work after fixation, however we are still in the process of fixing in our side and scheduled after a month

L1 Bithead

If it should work then what is the "fix" that is required on your side? Does my current version support Message Authentication? or is that the fix you are speaking of?

Hi @Eric Daoust​ 

 

As the community has not yet provided an answer to this question for some time, were you able to find a solution?

If so, we'd appreciate it if you could share it.

Your solution could help other community members who have similar questions.

 

Thanks, Liad.

L1 Bithead

No I have not received an appropriate answer as of yet

 

L7 Applicator

Hi @Eric Daoust​ 

 

In my understanding, CyberArk components that use RADIUS authentication should remain functional as long as the RADIUS server supports standard communication protocols and attributes.

 

The RADIUS upgrade should not interfere with regular authentication processes but must be verified for compatibility during testing.

 

I would recommend the following approach.

 

  1. Raise a Support case and confirm if there are any known issues reported by other customers having upgraded RADIUS for the same vulnerability.
  2. Consult with your team managing RADIUS to understand more about potential impact after fixing the vulnerability.
  3. I would definitely validate this in Test environment to find out whether is there an impact and to validate the authentication via RADIUS.

 

Hope it helps !

L0 Member

Hello,

 

did someone receive an answer on this?

 

We also need to enable the Message-Authenticator attribute flag for in our RADIUS server to mitigate the vulnerability, but we can't find any documentation on how to configure CyberArk to enable/disable sending the Message-Authenticator attirbute in each RADIUS authentication request.

 

Thanks.

  • 298 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!