Skip to content

Rasa Pro Missing Authentication For Voice Connector APIs

Moderate severity GitHub Reviewed Published Apr 17, 2025 in RasaHQ/security-advisories • Updated Apr 17, 2025

Package

pip rasa-pro (pip)

Affected versions

>= 3.12.0, <= 3.12.5
>= 3.11.0, <= 3.11.6
>= 3.10.0, <= 3.10.18
<= 3.9.17

Patched versions

3.12.6
3.11.7
3.10.19
3.9.20

Description

Vulnerability

A vulnerability has been identified in Rasa Pro where voice connectors in Rasa Pro do not properly implement authentication even when a token is configured in the credentials.yml file. This could allow an attacker to submit voice data to the Rasa Pro assistant from an unauthenticated source.

This impacts the following connectors:

  • audiocodes_stream
  • genesys
  • jambonz

As part of our investigation to resolve this issue, we have also performed a security review of our other voice channel connectors:

  • browser_audio: Does not support authentication. This is a development channel not intended for production use.
  • twilio_media_streams, twilio_voice and jambonz: Authentication is currently not supported by these channels, but our investigation has found a way for us to enable it for these voice channel connectors in a future Rasa Pro release.

Fix

The issue has been resolved for audiocodes, audiocodes_stream, and genesys connectors. Fixed versions of Rasa Pro have been released for 3.9.20, 3.10.19, 3.11.7 and 3.12.6. Please update to a fixed release.

If you are using one of the affected connectors, we strongly recommend upgrading to a fixed version. For connectors where authentication is not supported (e.g., Twilio), we suggest taking extra caution and considering other compensating controls if applicable.

References

@aerowithanl aerowithanl published to RasaHQ/security-advisories Apr 17, 2025
Published to the GitHub Advisory Database Apr 17, 2025
Reviewed Apr 17, 2025
Last updated Apr 17, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(14th percentile)

Weaknesses

CVE ID

CVE-2025-32377

GHSA ID

GHSA-7xq5-54jp-2mfg

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.