CyberAlerts is shutting down on June 30th, 2025. Thank you for your support!
Threat and Vulnerability Intelligence Database
Example Searches:
CVE
Threat Actors
Countries
Vendors
Severity
Known Exploited
|
Description: BOART & WIRE S.R.L Has Fallen Victim to Sarcoma Ransomware
January 14th, 2025 (6 months ago)
|
|
|
Description: The U.S. Department of Justice announced today that the FBI has deleted Chinese PlugX malware from over 4,200 computers in networks across the United States. [...]
January 14th, 2025 (6 months ago)
|
|
|
Description: A Threat Actor Claims to be Selling the Data of Nazareth District Court Israel
January 14th, 2025 (6 months ago)
|
|
|
Description: DEFACER KAMPUNG Defaced the Website of ICMS
January 14th, 2025 (6 months ago)
|
|
|
Description: Vulnerability
A vulnerability has been identified in Rasa Pro and Rasa Open Source that enables an attacker who has the ability to load a maliciously crafted model remotely into a Rasa instance to achieve Remote Code Execution.
The prerequisites for this are:
The HTTP API must be enabled on the Rasa instance eg with --enable-api. This is not the default configuration.
For unauthenticated RCE to be exploitable, the user must not have configured any authentication or other security controls recommended in our documentation.
For authenticated RCE, the attacker must posses a valid authentication token or JWT to interact with the Rasa API.
Fix
We encourage you to upgrade to a version of Rasa that includes a fix. These are:
Rasa Pro 3.8.18, 3.9.16, 3.10.12
Rasa Open Source 3.6.21
Once you have upgraded your Rasa Pro or Open Source installation, you will need to retrain your model using the fixed version of Rasa Pro or Open Source. If you have a custom component that inherits from one of the components listed below and modified the persist or load method, make sure to update your code. Please contact us in case you encounter any problems.
Affected components:
CountVectorFeaturizer
LexicalSyntacticFeaturizer
LogisticRegressionClassifier
SklearnIntentClassifier
DIETClassifier
CRFEntityExtractor
TrackerFeaturizer
TEDPolicy
UnexpectedIntentTEDPolicy
If you are unable to upgrade immediately, please follow our mitigation advice below.
Mitigation Advice
The unauthenticated RCE ca...
January 14th, 2025 (6 months ago)
|
|
|
Description: Vulnerability
A vulnerability has been identified in Rasa Pro and Rasa Open Source that enables an attacker who has the ability to load a maliciously crafted model remotely into a Rasa instance to achieve Remote Code Execution.
The prerequisites for this are:
The HTTP API must be enabled on the Rasa instance eg with --enable-api. This is not the default configuration.
For unauthenticated RCE to be exploitable, the user must not have configured any authentication or other security controls recommended in our documentation.
For authenticated RCE, the attacker must posses a valid authentication token or JWT to interact with the Rasa API.
Fix
We encourage you to upgrade to a version of Rasa that includes a fix. These are:
Rasa Pro 3.8.18, 3.9.16, 3.10.12
Rasa Open Source 3.6.21
Once you have upgraded your Rasa Pro or Open Source installation, you will need to retrain your model using the fixed version of Rasa Pro or Open Source. If you have a custom component that inherits from one of the components listed below and modified the persist or load method, make sure to update your code. Please contact us in case you encounter any problems.
Affected components:
CountVectorFeaturizer
LexicalSyntacticFeaturizer
LogisticRegressionClassifier
SklearnIntentClassifier
DIETClassifier
CRFEntityExtractor
TrackerFeaturizer
TEDPolicy
UnexpectedIntentTEDPolicy
If you are unable to upgrade immediately, please follow our mitigation advice below.
Mitigation Advice
The unauthenticated RCE ca...
January 14th, 2025 (6 months ago)
|
|
|
Description: Problem
A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method.
Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions:
the user opens a malicious link, such as one sent via email.
the user visits a compromised or manipulated website while the following settings are misconfigured:
security.backend.enforceReferrer feature is disabled,
BE/cookieSameSite configuration is set to lax or none
The vulnerability in the affected downstream component “Backend User Module” allows attackers to initiate password resets for other backend users or to terminate their user sessions.
Solution
Update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS that fix the problem described.
Credits
Thanks to Gabriel Dimitrov who reported this issue and to TYPO3 core and security members Benjamin Franzke, Oliver Hader, Andreas Kienast, Torben Hansen, Elias Häußler who fixed the issue.
References
TYPO3-CORE-SA-2025-004
References
https://github.com/TYPO3/typo3/security/advisories/GHSA-6w4x-gcx3-8p7v
https://github.co...
January 14th, 2025 (6 months ago)
|
|
|
Description: Problem
A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method.
Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions:
the user opens a malicious link, such as one sent via email.
the user visits a compromised or manipulated website while the following settings are misconfigured:
security.backend.enforceReferrer feature is disabled,
BE/cookieSameSite configuration is set to lax or none
The vulnerability in the affected downstream component “Dashboard Module” allows attackers to manipulate the victim’s dashboard configuration.
Solution
Update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS that fix the problem described.
Credits
Thanks to Gabriel Dimitrov who reported this issue and to TYPO3 core and security members Benjamin Franzke, Oliver Hader, Andreas Kienast, Torben Hansen, Elias Häußler who fixed the issue.
References
TYPO3-CORE-SA-2025-005
References
https://github.com/TYPO3/typo3/security/advisories/GHSA-qwx7-39pw-2mhr
https://github.com/TYPO3-CMS/dashboard/commit/c2e5dbdda87...
January 14th, 2025 (6 months ago)
|
|
|
[typo3/cms-extensionmanager] TYPO3 Extension Manager Module vulnerable to Cross-Site Request Forgery
Description: Problem
A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method.
Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions:
the user opens a malicious link, such as one sent via email.
the user visits a compromised or manipulated website while the following settings are misconfigured:
security.backend.enforceReferrer feature is disabled,
BE/cookieSameSite configuration is set to lax or none
The vulnerability in the affected downstream component “Extension Manager Module” allows attackers to retrieve and install 3rd party extensions from the TYPO3 Extension Repository - which can lead to remote code execution in the worst case.
Solution
Update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS that fix the problem described.
Credits
Thanks to Gabriel Dimitrov who reported this issue and to TYPO3 core and security members Benjamin Franzke, Oliver Hader, Andreas Kienast, Torben Hansen, Elias Häußler who fixed the issue.
References
TYPO3-CORE-SA-2025-006
References
https://github.com/TYPO3/typo3...
January 14th, 2025 (6 months ago)
|
|
|
Description: Problem
A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method.
Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions:
the user opens a malicious link, such as one sent via email.
the user visits a compromised or manipulated website while the following settings are misconfigured:
security.backend.enforceReferrer feature is disabled,
BE/cookieSameSite configuration is set to lax or none
The vulnerability in the affected downstream component “Form Framework Module” allows attackers to manipulate or delete persisted form definitions.
Solution
Update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS that fix the problem described.
Credits
Thanks to Gabriel Dimitrov who reported this issue and to TYPO3 core and security members Benjamin Franzke, Oliver Hader, Andreas Kienast, Torben Hansen, Elias Häußler who fixed the issue.
References
TYPO3-CORE-SA-2025-007
References
https://github.com/TYPO3/typo3/security/advisories/GHSA-ww7h-g2qf-7xv6
https://github.com/TYPO3-CMS/form/commit/93327743f5d...
January 14th, 2025 (6 months ago)
|