Another new CVE for an old critical ../ by Fortinet.

https://www.fortiguard.com/psirt/FG-IR-23-085

sev:CRIT 9.9 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

A relative path traversal in Fortinet FortiSIEM versions 7.0.0, 6.7.0 through 6.7.2, 6.6.0 through 6.6.3, 6.5.1, 6.5.0 allows attacker to escalate privilege via uploading certain GUI elements

https://nvd.nist.gov/vuln/detail/CVE-2023-40714

Another new CVE for an old critical ../ by Fortinet.

https://www.fortiguard.com/psirt/FG-IR-23-085

sev:CRIT 9.9 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

A relative path traversal in Fortinet FortiSIEM versions 7.0.0, 6.7.0 through 6.7.2, 6.6.0 through 6.6.3, 6.5.1, 6.5.0 allows attacker to escalate privilege via uploading certain GUI elements

https://nvd.nist.gov/vuln/detail/CVE-2023-40714

Ooh, vulns in Moxa kit released today.

https://www.moxa.com/en/support/product-support/security-advisory/mpsa-259491-cve-2025-0415-command-injection-leading-to-denial-of-service-(dos)

sev:CRIT 9.2 - CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:H

A remote attacker with web administrator privileges can exploit the device’s web interface to execute arbitrary system commands through the NTP settings. Successful exploitation may result in the device entering an infinite reboot loop, leading to a total or partial denial of connectivity for downstream systems that rely on its network services.

https://nvd.nist.gov/vuln/detail/CVE-2025-0415

https://www.moxa.com/en/support/product-support/security-advisory/mpsa-259491-cve-2025-0676-command-injection-leading-to-privilege-escalation

sev:HIGH 8.6 - CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

This vulnerability involves command injection in tcpdump within Moxa products, enabling an authenticated attacker with console access to exploit improper input validation to inject and execute systems commands. Successful exploitation could result in privilege escalation, allowing the attacker to gain root shell access and maintain persistent control over the device, potentially disrupting network services and affecting the availability of downstream systems that rely on its connectivity.

https://nvd.nist.gov/vuln/detail/CVE-2025-0676

Ooh, vulns in Moxa kit released today.

https://www.moxa.com/en/support/product-support/security-advisory/mpsa-259491-cve-2025-0415-command-injection-leading-to-denial-of-service-(dos)

sev:CRIT 9.2 - CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:H

A remote attacker with web administrator privileges can exploit the device’s web interface to execute arbitrary system commands through the NTP settings. Successful exploitation may result in the device entering an infinite reboot loop, leading to a total or partial denial of connectivity for downstream systems that rely on its network services.

https://nvd.nist.gov/vuln/detail/CVE-2025-0415

https://www.moxa.com/en/support/product-support/security-advisory/mpsa-259491-cve-2025-0676-command-injection-leading-to-privilege-escalation

sev:HIGH 8.6 - CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

This vulnerability involves command injection in tcpdump within Moxa products, enabling an authenticated attacker with console access to exploit improper input validation to inject and execute systems commands. Successful exploitation could result in privilege escalation, allowing the attacker to gain root shell access and maintain persistent control over the device, potentially disrupting network services and affecting the availability of downstream systems that rely on its connectivity.

https://nvd.nist.gov/vuln/detail/CVE-2025-0676

Ooh, vulns in Moxa kit released today.

https://www.moxa.com/en/support/product-support/security-advisory/mpsa-259491-cve-2025-0415-command-injection-leading-to-denial-of-service-(dos)

sev:CRIT 9.2 - CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:H

A remote attacker with web administrator privileges can exploit the device’s web interface to execute arbitrary system commands through the NTP settings. Successful exploitation may result in the device entering an infinite reboot loop, leading to a total or partial denial of connectivity for downstream systems that rely on its network services.

https://nvd.nist.gov/vuln/detail/CVE-2025-0415

https://www.moxa.com/en/support/product-support/security-advisory/mpsa-259491-cve-2025-0676-command-injection-leading-to-privilege-escalation

sev:HIGH 8.6 - CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

This vulnerability involves command injection in tcpdump within Moxa products, enabling an authenticated attacker with console access to exploit improper input validation to inject and execute systems commands. Successful exploitation could result in privilege escalation, allowing the attacker to gain root shell access and maintain persistent control over the device, potentially disrupting network services and affecting the availability of downstream systems that rely on its connectivity.

https://nvd.nist.gov/vuln/detail/CVE-2025-0676

Ooh, vulns in Moxa kit released today.

https://www.moxa.com/en/support/product-support/security-advisory/mpsa-259491-cve-2025-0415-command-injection-leading-to-denial-of-service-(dos)

sev:CRIT 9.2 - CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:H

A remote attacker with web administrator privileges can exploit the device’s web interface to execute arbitrary system commands through the NTP settings. Successful exploitation may result in the device entering an infinite reboot loop, leading to a total or partial denial of connectivity for downstream systems that rely on its network services.

https://nvd.nist.gov/vuln/detail/CVE-2025-0415

https://www.moxa.com/en/support/product-support/security-advisory/mpsa-259491-cve-2025-0676-command-injection-leading-to-privilege-escalation

sev:HIGH 8.6 - CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

This vulnerability involves command injection in tcpdump within Moxa products, enabling an authenticated attacker with console access to exploit improper input validation to inject and execute systems commands. Successful exploitation could result in privilege escalation, allowing the attacker to gain root shell access and maintain persistent control over the device, potentially disrupting network services and affecting the availability of downstream systems that rely on its connectivity.

https://nvd.nist.gov/vuln/detail/CVE-2025-0676

Zabbix published a few CVEs, including a couple sev:HIGH vulns.

https://support.zabbix.com/browse/ZBX-26257

sev:HIGH 8.6 - CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

A low privilege (regular) Zabbix user with API access can use SQL injection vulnerability in include/classes/api/CApiService.php to execute arbitrary SQL commands via the groupBy parameter.

https://nvd.nist.gov/vuln/detail/CVE-2024-36465

https://support.zabbix.com/browse/ZBX-26254

sev:HIGH 7.5 - CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

The endpoint /zabbix.php?action=export.valuemaps suffers from a Cross-Site Scripting vulnerability via the backurl parameter. This is caused by the reflection of user-supplied data without appropriate HTML escaping or output encoding. As a result, a JavaScript payload may be injected into the above endpoint causing it to be executed within the context of the victim's browser.

https://nvd.nist.gov/vuln/detail/CVE-2024-45699

Zabbix published a few CVEs, including a couple sev:HIGH vulns.

https://support.zabbix.com/browse/ZBX-26257

sev:HIGH 8.6 - CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

A low privilege (regular) Zabbix user with API access can use SQL injection vulnerability in include/classes/api/CApiService.php to execute arbitrary SQL commands via the groupBy parameter.

https://nvd.nist.gov/vuln/detail/CVE-2024-36465

https://support.zabbix.com/browse/ZBX-26254

sev:HIGH 7.5 - CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

The endpoint /zabbix.php?action=export.valuemaps suffers from a Cross-Site Scripting vulnerability via the backurl parameter. This is caused by the reflection of user-supplied data without appropriate HTML escaping or output encoding. As a result, a JavaScript payload may be injected into the above endpoint causing it to be executed within the context of the victim's browser.

https://nvd.nist.gov/vuln/detail/CVE-2024-45699

Zabbix published a few CVEs, including a couple sev:HIGH vulns.

https://support.zabbix.com/browse/ZBX-26257

sev:HIGH 8.6 - CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

A low privilege (regular) Zabbix user with API access can use SQL injection vulnerability in include/classes/api/CApiService.php to execute arbitrary SQL commands via the groupBy parameter.

https://nvd.nist.gov/vuln/detail/CVE-2024-36465

https://support.zabbix.com/browse/ZBX-26254

sev:HIGH 7.5 - CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

The endpoint /zabbix.php?action=export.valuemaps suffers from a Cross-Site Scripting vulnerability via the backurl parameter. This is caused by the reflection of user-supplied data without appropriate HTML escaping or output encoding. As a result, a JavaScript payload may be injected into the above endpoint causing it to be executed within the context of the victim's browser.

https://nvd.nist.gov/vuln/detail/CVE-2024-45699

Zabbix published a few CVEs, including a couple sev:HIGH vulns.

https://support.zabbix.com/browse/ZBX-26257

sev:HIGH 8.6 - CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

A low privilege (regular) Zabbix user with API access can use SQL injection vulnerability in include/classes/api/CApiService.php to execute arbitrary SQL commands via the groupBy parameter.

https://nvd.nist.gov/vuln/detail/CVE-2024-36465

https://support.zabbix.com/browse/ZBX-26254

sev:HIGH 7.5 - CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

The endpoint /zabbix.php?action=export.valuemaps suffers from a Cross-Site Scripting vulnerability via the backurl parameter. This is caused by the reflection of user-supplied data without appropriate HTML escaping or output encoding. As a result, a JavaScript payload may be injected into the above endpoint causing it to be executed within the context of the victim's browser.

https://nvd.nist.gov/vuln/detail/CVE-2024-45699

Aqua published a blog post on the TTPs ( including IOCs and samples ) used by an apparently CN-adjacent TA attacking Tomcat servers. The post doesn't specifically say that the vulnerability exploited is CVE-2025-24813 but in their mitigations section they say:

"Ensure that all vulnerabilities are patched. Particularly internet facing applications such as Tomcat servers. Vulnerabilities such as CVE-2025-24813 that are new, critical and actively exploited should be prioritized."

https://www.aquasec.com/blog/new-campaign-against-apache-tomcat/

CVE ID: CVE-2025-24813
Vendor: Apache
Product: Tomcat
Date Added: 2025-04-01
Vulnerability: Apache Tomcat Path Equivalence Vulnerability
Notes: https://lists.apache.org/thread/j5fkjv2k477os90nczf2v9l61fb0kkgq ; https://nvd.nist.gov/vuln/detail/CVE-2025-24813
CVE URL: https://nvd.nist.gov/vuln/detail/CVE-2025-24813

CISA has updated the KEV catalogue:

CVE-2025-24813: Apache Tomcat Path Equivalence Vulnerability https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=&field_date_added_wrapper=all&sort_by=field_date_added&items_per_page=20 #CISA #cybersecurity #infosec #Apache

Also:

Two Industrial Control Systems Advisories https://www.cisa.gov/news-events/alerts/2025/04/01/cisa-releases-two-industrial-control-systems-advisories

Looks like CISA is now satisfied and has added CVE-2025-24813 (Apache Tomcat Path Equivalence Vulnerability ) to the KEV Catalog.

Aqua published a blog post on the TTPs ( including IOCs and samples ) used by an apparently CN-adjacent TA attacking Tomcat servers. The post doesn't specifically say that the vulnerability exploited is CVE-2025-24813 but in their mitigations section they say:

"Ensure that all vulnerabilities are patched. Particularly internet facing applications such as Tomcat servers. Vulnerabilities such as CVE-2025-24813 that are new, critical and actively exploited should be prioritized."

https://www.aquasec.com/blog/new-campaign-against-apache-tomcat/

CVE ID: CVE-2025-24813
Vendor: Apache
Product: Tomcat
Date Added: 2025-04-01
Vulnerability: Apache Tomcat Path Equivalence Vulnerability
Notes: https://lists.apache.org/thread/j5fkjv2k477os90nczf2v9l61fb0kkgq ; https://nvd.nist.gov/vuln/detail/CVE-2025-24813
CVE URL: https://nvd.nist.gov/vuln/detail/CVE-2025-24813

CISA has updated the KEV catalogue:

CVE-2025-24813: Apache Tomcat Path Equivalence Vulnerability https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=&field_date_added_wrapper=all&sort_by=field_date_added&items_per_page=20 #CISA #cybersecurity #infosec #Apache

Also:

Two Industrial Control Systems Advisories https://www.cisa.gov/news-events/alerts/2025/04/01/cisa-releases-two-industrial-control-systems-advisories

Looks like CISA is now satisfied and has added CVE-2025-24813 (Apache Tomcat Path Equivalence Vulnerability ) to the KEV Catalog.

Apache Tomcat Vulnerability (CVE-2025-24813) Exploited to Execute Code on Servers https://cybersecuritynews.com/apache-tomcat-vulnerability-exploited/ #CyberSecurityNews #VulnerabilityNews #cybersecuritynews #CyberSecurity #cybersecurity #vulnerability

Fortinet added CVE-2025-24813, Apache Tomcat RCE (high) to its outbreak alerts yesterday: https://www.fortinet.com/fortiguard/labs @fortinet #cybersecurity #infosec #Apache

Details: https://fortiguard.fortinet.com/outbreak-alert/apache-tomcat-rce

(recordedfuture.com) Apache Tomcat: Critical Path Equivalence Vulnerability (CVE-2025-24813) NOT (yet) under active exploitation

https://www.recordedfuture.com/blog/apache-tomcat-cve-2025-24813-vulnerability-analysis

Insikt Group notes specifically that this vulnerability has not yet been observed as being actively exploited in the wild.

Summary:
This article details CVE-2025-24813, a critical path equivalence vulnerability in Apache Tomcat that allows unauthenticated remote code execution under specific conditions. The vulnerability affects multiple Tomcat versions (11.0.0-M1 to 11.0.2, 10.1.0-M1 to 10.1.34, 9.0.0-M1 to 9.0.98, and most 8.5.x versions). Greynoise has identified six malicious IP addresses attempting to exploit this vulnerability, targeting systems in the US, Japan, Mexico, South Korea, and Australia. Multiple proof-of-concept exploits have been published, increasing the risk of exploitation. Organizations are advised to upgrade to patched versions (11.0.3, 10.1.35, or 9.0.99) or implement network-level controls if immediate patching isn't possible.

#Cybersecurity #ThreatIntel #Tomcat #ActiveExploitation #ITW #Exploitation #Vulnerability #CVE202524813

Researchers, you don't need to be this patient. Just publish that shit.

https://medium.com/@mihat2/onlyoffice-document-server-path-traversal-fdd573fec291

Directory Traversal vulnerability in ONLYOFFICE Document Server v.7.5.0 and before allows a remote attacker to obtain sensitive information via a crafted file upload.

• October 10, 2023 – The moment I realized the flaw was real, I immediately reached out to ONLYOFFICE’s security team. To my surprise, they responded the same day! To ensure they had all the details, I sent them a thorough PDF report outlining the vulnerability, complete with technical analysis, proof-of-concept, and potential impact. I thought this was going to be a smooth disclosure process — how wrong I was.
• October 11 — November 19, 2023 — I followed up. Again. And again. Silence. Maybe my emails were lost? Maybe they were ignoring me? Either way, weeks passed, and still — no response.
• November 20, 2023 – We submitted the vulnerability to HackerOne, hoping to reach the ONLYOFFICE through another channel.
• December 4, 2023 – With no response from HackerOne, we escalated the report to HackerOne Disclosure Assistance, but STILL received no response.
• February 19, 2024 – ONLYOFFICE finally responded, stating that they were working on a fix.
• February 26, 2024 – ONLYOFFICE released a fix for the vulnerability.
• April 1, 2024 – ONLYOFFICE informed us that while the fix was available, some products would not receive the security patch until Summer 2024. They requested that we delay public disclosure until July 2024.
• February 21, 2025 – HackerOne Disclosure Assistance responded, stating that they were reviewing the backlog and asked for an update on the current situation.

https://nvd.nist.gov/vuln/detail/CVE-2023-46988

Researchers, you don't need to be this patient. Just publish that shit.

https://medium.com/@mihat2/onlyoffice-document-server-path-traversal-fdd573fec291

Directory Traversal vulnerability in ONLYOFFICE Document Server v.7.5.0 and before allows a remote attacker to obtain sensitive information via a crafted file upload.

• October 10, 2023 – The moment I realized the flaw was real, I immediately reached out to ONLYOFFICE’s security team. To my surprise, they responded the same day! To ensure they had all the details, I sent them a thorough PDF report outlining the vulnerability, complete with technical analysis, proof-of-concept, and potential impact. I thought this was going to be a smooth disclosure process — how wrong I was.
• October 11 — November 19, 2023 — I followed up. Again. And again. Silence. Maybe my emails were lost? Maybe they were ignoring me? Either way, weeks passed, and still — no response.
• November 20, 2023 – We submitted the vulnerability to HackerOne, hoping to reach the ONLYOFFICE through another channel.
• December 4, 2023 – With no response from HackerOne, we escalated the report to HackerOne Disclosure Assistance, but STILL received no response.
• February 19, 2024 – ONLYOFFICE finally responded, stating that they were working on a fix.
• February 26, 2024 – ONLYOFFICE released a fix for the vulnerability.
• April 1, 2024 – ONLYOFFICE informed us that while the fix was available, some products would not receive the security patch until Summer 2024. They requested that we delay public disclosure until July 2024.
• February 21, 2025 – HackerOne Disclosure Assistance responded, stating that they were reviewing the backlog and asked for an update on the current situation.

https://nvd.nist.gov/vuln/detail/CVE-2023-46988

Simple and practical vulns like this are always nice to read about and learn from and replicate.

https://github.com/remix-run/react-router/security/advisories/GHSA-4q56-crqp-v477

sev:HIGH 7.5 - CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

React Router is a multi-strategy router for React bridging the gap from React 18 to React 19. There is a vulnerability in Remix/React Router that affects all Remix 2 and React Router 7 consumers using the Express adapter. Basically, this vulnerability allows anyone to spoof the URL used in an incoming Request by putting a URL pathname in the port section of a URL that is part of a Host or X-Forwarded-Host header sent to a Remix/React Router request handler. This issue has been patched and released in Remix 2.16.3 and React Router 7.4.1.

https://nvd.nist.gov/vuln/detail/CVE-2025-31137

Simple and practical vulns like this are always nice to read about and learn from and replicate.

https://github.com/remix-run/react-router/security/advisories/GHSA-4q56-crqp-v477

sev:HIGH 7.5 - CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

React Router is a multi-strategy router for React bridging the gap from React 18 to React 19. There is a vulnerability in Remix/React Router that affects all Remix 2 and React Router 7 consumers using the Express adapter. Basically, this vulnerability allows anyone to spoof the URL used in an incoming Request by putting a URL pathname in the port section of a URL that is part of a Host or X-Forwarded-Host header sent to a Remix/React Router request handler. This issue has been patched and released in Remix 2.16.3 and React Router 7.4.1.

https://nvd.nist.gov/vuln/detail/CVE-2025-31137

Patch your Mozilla things. They released an advisory for Firefox and Thunderbird with four sev:HIGH vulns.

https://www.mozilla.org/en-US/security/advisories/mfsa2025-20/

CVE-2025-3028: Use-after-free triggered by XSLTProcessor

CVE-2025-3031: JIT optimization bug with different stack slot sizes

CVE-2025-3032: Leaking file descriptors from the fork server

CVE-2025-3029: URL bar spoofing via non-BMP Unicode characters

CVE-2025-3035: Tab title disclosure across pages when using AI chatbot

CVE-2025-3033: Opening local .url files could lead to another file being opened

CVE-2025-3030: Memory safety bugs fixed in Firefox 137, Thunderbird 137, Firefox ESR 128.9, and Thunderbird 128.9

CVE-2025-3034: Memory safety bugs fixed in Firefox 137 and Thunderbird 137

Patch your Mozilla things. They released an advisory for Firefox and Thunderbird with four sev:HIGH vulns.

https://www.mozilla.org/en-US/security/advisories/mfsa2025-20/

CVE-2025-3028: Use-after-free triggered by XSLTProcessor

CVE-2025-3031: JIT optimization bug with different stack slot sizes

CVE-2025-3032: Leaking file descriptors from the fork server

CVE-2025-3029: URL bar spoofing via non-BMP Unicode characters

CVE-2025-3035: Tab title disclosure across pages when using AI chatbot

CVE-2025-3033: Opening local .url files could lead to another file being opened

CVE-2025-3030: Memory safety bugs fixed in Firefox 137, Thunderbird 137, Firefox ESR 128.9, and Thunderbird 128.9

CVE-2025-3034: Memory safety bugs fixed in Firefox 137 and Thunderbird 137

Patch your Mozilla things. They released an advisory for Firefox and Thunderbird with four sev:HIGH vulns.

https://www.mozilla.org/en-US/security/advisories/mfsa2025-20/

CVE-2025-3028: Use-after-free triggered by XSLTProcessor

CVE-2025-3031: JIT optimization bug with different stack slot sizes

CVE-2025-3032: Leaking file descriptors from the fork server

CVE-2025-3029: URL bar spoofing via non-BMP Unicode characters

CVE-2025-3035: Tab title disclosure across pages when using AI chatbot

CVE-2025-3033: Opening local .url files could lead to another file being opened

CVE-2025-3030: Memory safety bugs fixed in Firefox 137, Thunderbird 137, Firefox ESR 128.9, and Thunderbird 128.9

CVE-2025-3034: Memory safety bugs fixed in Firefox 137 and Thunderbird 137

Patch your Mozilla things. They released an advisory for Firefox and Thunderbird with four sev:HIGH vulns.

https://www.mozilla.org/en-US/security/advisories/mfsa2025-20/

CVE-2025-3028: Use-after-free triggered by XSLTProcessor

CVE-2025-3031: JIT optimization bug with different stack slot sizes

CVE-2025-3032: Leaking file descriptors from the fork server

CVE-2025-3029: URL bar spoofing via non-BMP Unicode characters

CVE-2025-3035: Tab title disclosure across pages when using AI chatbot

CVE-2025-3033: Opening local .url files could lead to another file being opened

CVE-2025-3030: Memory safety bugs fixed in Firefox 137, Thunderbird 137, Firefox ESR 128.9, and Thunderbird 128.9

CVE-2025-3034: Memory safety bugs fixed in Firefox 137 and Thunderbird 137

Patch your Mozilla things. They released an advisory for Firefox and Thunderbird with four sev:HIGH vulns.

https://www.mozilla.org/en-US/security/advisories/mfsa2025-20/

CVE-2025-3028: Use-after-free triggered by XSLTProcessor

CVE-2025-3031: JIT optimization bug with different stack slot sizes

CVE-2025-3032: Leaking file descriptors from the fork server

CVE-2025-3029: URL bar spoofing via non-BMP Unicode characters

CVE-2025-3035: Tab title disclosure across pages when using AI chatbot

CVE-2025-3033: Opening local .url files could lead to another file being opened

CVE-2025-3030: Memory safety bugs fixed in Firefox 137, Thunderbird 137, Firefox ESR 128.9, and Thunderbird 128.9

CVE-2025-3034: Memory safety bugs fixed in Firefox 137 and Thunderbird 137

CrushFTP Authentication Bypass - CVE-2025-2825
#CVE_2025_2825
https://projectdiscovery.io/blog/crushftp-authentication-bypass

CrushFTP CVE-2025-2825 flaw actively exploited in the wild – Source: securityaffairs.com https://ciso2ciso.com/crushftp-cve-2025-2825-flaw-actively-exploited-in-the-wild-source-securityaffairs-com/ #rssfeedpostgeneratorecho #informationsecuritynews #ITInformationSecurity #SecurityAffairscom #CyberSecurityNews #PierluigiPaganini #SecurityAffairs #SecurityAffairs #BreakingNews #SecurityNews #hackingnews #CrushFTP #Security #hacking

Attackers are targeting CrushFTP vulnerability with public PoC (CVE-2025-2825) https://www.helpnetsecurity.com/2025/04/01/crushftp-vulnerability-exploitation-cve-2025-2825/ #Shadowserver #Don'tmiss #VulnCheck #Hotstuff #CrushFTP #Rapid7 #News #CVE #PoC

CrushFTP Authentication Bypass - CVE-2025-2825 — ProjectDiscovery Blog https://projectdiscovery.io/blog/crushftp-authentication-bypass

Full technical analysis of CrushFTP CVE-2025-2825 here c/o @fuzz, and props to the Project Discovery folks who look to have come up with the same findings https://attackerkb.com/topics/k0EgiL9Psz/cve-2025-2825/rapid7-analysis

CrushFTP: Patch critical vulnerability ASAP! (CVE-2025-2825) https://www.helpnetsecurity.com/2025/03/27/crushftp-vulnerability-cve-2025-2825/ #securityupdate #vulnerability #file-sharing #enterprise #Don'tmiss #Hotstuff #CrushFTP #News #SMBs

🚨CVE-2025-2825: Unauthenticated HTTP(S) port access on CrushFTPv10/v11

CVSS: 9.8

https://darkwebinformer.com/cve-2025-2825-unauthenticated-http-s-port-access-on-crushftpv10-v11/

The CrushFTP CVE that @catc0n has been talking about is finally published.

https://www.crushftp.com/crush11wiki/Wiki.jsp?page=Update

sev:CRIT 9.8 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CrushFTP versions 10.0.0 through 10.8.3 and 11.0.0 through 11.3.0 are affected by a vulnerability that may result in unauthenticated access. Remote and unauthenticated HTTP requests to CrushFTP may allow attackers to gain unauthorized access.

https://nvd.nist.gov/vuln/detail/CVE-2025-2825

Our pals over at VulnCheck very kindly assigned a CVE for the CrushFTP issue since CrushFTP appears reluctant to do the needful directly (thx @albinolobster!)

https://www.cve.org/cverecord?id=CVE-2025-2825

This looks like a small project and I'm not trying to throw stones here. I am posting this as a legitimate learning opportunity for people.

https://github.com/Scratch-Coding-Hut/Scratch-Coding-Hut.github.io/security/advisories/GHSA-mmg3-567w-v9j2

sev:CRIT 9.0 - CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

scratch-coding-hut.github.io is the website for Coding Hut. In 1.0-beta3 and earlier, the login link can be used to login to any account by changing the username in the username field.

So basically you can use a login link to login to any account you want to hack into without any effort. We need to fix this! There is a username thingy that you can use to hack into any account, but please don’t abuse this feature!

https://nvd.nist.gov/vuln/detail/CVE-2025-31122

I for one like seeing command exec in Rockwell Automation products.

https://www.rockwellautomation.com/en-us/trust-center/security-advisories/advisory.SD1723.html

sev:CRIT 9.1 - CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

A vulnerability exists in the Rockwell Automation Verve Asset Manager due to insufficient variable sanitizing. A portion of the administrative web interface for Verve's Legacy Agentless Device Inventory (ADI) capability (deprecated since the 1.36 release) allows users to change a variable with inadequate sanitizing. If exploited, it could allow a threat actor with administrative access to run arbitrary commands in the context of the container running the service.

https://nvd.nist.gov/vuln/detail/CVE-2025-1449

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

LPE in VMWare Aria Operations.

https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/25541

sev:HIGH 7.8 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

VMware Aria Operations contains a local privilege escalation vulnerability. A malicious actor with local administrative privileges can escalate their privileges to root on the appliance running VMware Aria Operations.

https://nvd.nist.gov/vuln/detail/CVE-2025-22231

LPE in VMWare Aria Operations.

https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/25541

sev:HIGH 7.8 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

VMware Aria Operations contains a local privilege escalation vulnerability. A malicious actor with local administrative privileges can escalate their privileges to root on the appliance running VMware Aria Operations.

https://nvd.nist.gov/vuln/detail/CVE-2025-22231

Patch your Mozilla things. They released an advisory for Firefox and Thunderbird with four sev:HIGH vulns.

https://www.mozilla.org/en-US/security/advisories/mfsa2025-20/

CVE-2025-3028: Use-after-free triggered by XSLTProcessor

CVE-2025-3031: JIT optimization bug with different stack slot sizes

CVE-2025-3032: Leaking file descriptors from the fork server

CVE-2025-3029: URL bar spoofing via non-BMP Unicode characters

CVE-2025-3035: Tab title disclosure across pages when using AI chatbot

CVE-2025-3033: Opening local .url files could lead to another file being opened

CVE-2025-3030: Memory safety bugs fixed in Firefox 137, Thunderbird 137, Firefox ESR 128.9, and Thunderbird 128.9

CVE-2025-3034: Memory safety bugs fixed in Firefox 137 and Thunderbird 137

I don't know Apache Pinot but this seems like a good one to keep in your back pocket.

https://lists.apache.org/thread/ksf8qsndr1h66otkbjz2wrzsbw992r8v

Authentication Bypass Issue

If the path does not contain / and contain., authentication is not required.

Expected Normal Request and Response Example

curl -X POST -H "Content-Type: application/json" -d {\"username\":\"hack2\",\"password\":\"hack\",\"component\":\"CONTROLLER\",\"role\":\"ADMIN\",\"tables\":[],\"permissions\":[],\"usernameWithComponent\":\"hack_CONTROLLER\"} http://{server_ip}:9000/users

Return: {"code":401,"error":"HTTP 401 Unauthorized"}

Malicious Request and Response Example

curl -X POST -H "Content-Type: application/json" -d '{\"username\":\"hack\",\"password\":\"hack\",\"component\":\"CONTROLLER\",\"role\":\"ADMIN\",\"tables\":[],\"permissions\":[],\"usernameWithComponent\":\"hack_CONTROLLER\"}' http://{serverip}:9000/users; http://{serverip}:9000/users; .

Return: {"users":{}}

https://nvd.nist.gov/vuln/detail/CVE-2024-56325

I don't know Apache Pinot but this seems like a good one to keep in your back pocket.

https://lists.apache.org/thread/ksf8qsndr1h66otkbjz2wrzsbw992r8v

Authentication Bypass Issue

If the path does not contain / and contain., authentication is not required.

Expected Normal Request and Response Example

curl -X POST -H "Content-Type: application/json" -d {\"username\":\"hack2\",\"password\":\"hack\",\"component\":\"CONTROLLER\",\"role\":\"ADMIN\",\"tables\":[],\"permissions\":[],\"usernameWithComponent\":\"hack_CONTROLLER\"} http://{server_ip}:9000/users

Return: {"code":401,"error":"HTTP 401 Unauthorized"}

Malicious Request and Response Example

curl -X POST -H "Content-Type: application/json" -d '{\"username\":\"hack\",\"password\":\"hack\",\"component\":\"CONTROLLER\",\"role\":\"ADMIN\",\"tables\":[],\"permissions\":[],\"usernameWithComponent\":\"hack_CONTROLLER\"}' http://{serverip}:9000/users; http://{serverip}:9000/users; .

Return: {"users":{}}

https://nvd.nist.gov/vuln/detail/CVE-2024-56325

And we have a perfect 10 in Apache Parquet, whatever that is. 🥳

sev:CRIT 10.0 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Schema parsing in the parquet-avro module of Apache Parquet 1.15.0 and previous versions allows bad actors to execute arbitrary code

Users are recommended to upgrade to version 1.15.1, which fixes the issue.

https://nvd.nist.gov/vuln/detail/CVE-2025-30065

And we have a perfect 10 in Apache Parquet, whatever that is. 🥳

sev:CRIT 10.0 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Schema parsing in the parquet-avro module of Apache Parquet 1.15.0 and previous versions allows bad actors to execute arbitrary code

Users are recommended to upgrade to version 1.15.1, which fixes the issue.

https://nvd.nist.gov/vuln/detail/CVE-2025-30065

CVE-2024-55963: Unauthenticated RCE in Default-Install of Appsmith https://rhinosecuritylabs.com/research/cve-2024-55963-unauthenticated-rce-in-appsmith/

That RCE in Appsmith from December has a write-up.

https://rhinosecuritylabs.com/research/cve-2024-55963-unauthenticated-rce-in-appsmith/

https://github.com/appsmithorg/appsmith/releases/tag/v1.52

While reviewing the Appsmith Enterprise platform, Rhino Security Labs uncovered a series of critical vulnerabilities affecting default installations of the product. Most severe among them is CVE-2024-55963, which allows unauthenticated remote code execution due to a misconfigured PostgreSQL database included by default. Two additional vulnerabilities (CVE-2024-55964 and CVE-2024-55965) enable unauthorized access to sensitive data and application denial of service.

Unfortunately, the CVE still isn't in NVD.

https://nvd.nist.gov/vuln/detail/CVE-2024-55963

That RCE in Appsmith from December has a write-up.

https://rhinosecuritylabs.com/research/cve-2024-55963-unauthenticated-rce-in-appsmith/

https://github.com/appsmithorg/appsmith/releases/tag/v1.52

While reviewing the Appsmith Enterprise platform, Rhino Security Labs uncovered a series of critical vulnerabilities affecting default installations of the product. Most severe among them is CVE-2024-55963, which allows unauthenticated remote code execution due to a misconfigured PostgreSQL database included by default. Two additional vulnerabilities (CVE-2024-55964 and CVE-2024-55965) enable unauthorized access to sensitive data and application denial of service.

Unfortunately, the CVE still isn't in NVD.

https://nvd.nist.gov/vuln/detail/CVE-2024-55963

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

Three new CVEs in Autodesk Navisworks this morning. All three are sev:HIGH 7.8 - CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

https://www.autodesk.com/trust/security-advisories/adsk-sa-2025-0002

CVE-2025-1658: A maliciously crafted DWFX file, when parsed through Autodesk Navisworks, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.

CVE-2025-1659: A maliciously crafted DWFX file, when parsed through Autodesk Navisworks, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.

CVE-2025-1660: A maliciously crafted DWFX file, when parsed through Autodesk Navisworks, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.

Three new CVEs in Autodesk Navisworks this morning. All three are sev:HIGH 7.8 - CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

https://www.autodesk.com/trust/security-advisories/adsk-sa-2025-0002

CVE-2025-1658: A maliciously crafted DWFX file, when parsed through Autodesk Navisworks, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.

CVE-2025-1659: A maliciously crafted DWFX file, when parsed through Autodesk Navisworks, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.

CVE-2025-1660: A maliciously crafted DWFX file, when parsed through Autodesk Navisworks, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.

Patch your Mozilla things. They released an advisory for Firefox and Thunderbird with four sev:HIGH vulns.

https://www.mozilla.org/en-US/security/advisories/mfsa2025-20/

CVE-2025-3028: Use-after-free triggered by XSLTProcessor

CVE-2025-3031: JIT optimization bug with different stack slot sizes

CVE-2025-3032: Leaking file descriptors from the fork server

CVE-2025-3029: URL bar spoofing via non-BMP Unicode characters

CVE-2025-3035: Tab title disclosure across pages when using AI chatbot

CVE-2025-3033: Opening local .url files could lead to another file being opened

CVE-2025-3030: Memory safety bugs fixed in Firefox 137, Thunderbird 137, Firefox ESR 128.9, and Thunderbird 128.9

CVE-2025-3034: Memory safety bugs fixed in Firefox 137 and Thunderbird 137

Patch your Mozilla things. They released an advisory for Firefox and Thunderbird with four sev:HIGH vulns.

https://www.mozilla.org/en-US/security/advisories/mfsa2025-20/

CVE-2025-3028: Use-after-free triggered by XSLTProcessor

CVE-2025-3031: JIT optimization bug with different stack slot sizes

CVE-2025-3032: Leaking file descriptors from the fork server

CVE-2025-3029: URL bar spoofing via non-BMP Unicode characters

CVE-2025-3035: Tab title disclosure across pages when using AI chatbot

CVE-2025-3033: Opening local .url files could lead to another file being opened

CVE-2025-3030: Memory safety bugs fixed in Firefox 137, Thunderbird 137, Firefox ESR 128.9, and Thunderbird 128.9

CVE-2025-3034: Memory safety bugs fixed in Firefox 137 and Thunderbird 137

Three new CVEs in Autodesk Navisworks this morning. All three are sev:HIGH 7.8 - CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

https://www.autodesk.com/trust/security-advisories/adsk-sa-2025-0002

CVE-2025-1658: A maliciously crafted DWFX file, when parsed through Autodesk Navisworks, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.

CVE-2025-1659: A maliciously crafted DWFX file, when parsed through Autodesk Navisworks, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.

CVE-2025-1660: A maliciously crafted DWFX file, when parsed through Autodesk Navisworks, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.

CVE-2025-24259: Leaking Bookmarks on macOS

https://wts.dev/posts/bookmarks-leak/

#HackerNews #CVE202524259 #macOS #Bookmarks #Security #Vulnerability #HackerNews #Cybersecurity

NCSC Finland published some vulns in Valmet DNA, which is a DCS system. Those are always fun to attack and / or defend.

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0416/

sev:HIGH 8.9 - CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:N/AU:Y/R:U/V:D/RE:H/U:Amber

Local privilege escalation through insecure DCOM configuration in Valmet DNA versions prior to C2023. The DCOM object Valmet DNA Engineering has permissions that allow it to run commands as a user with the SeImpersonatePrivilege privilege. The SeImpersonatePrivilege privilege is a Windows permission that allows a process to impersonate another user. An attacker can use this vulnerability to escalate their privileges and take complete control of the system.

https://nvd.nist.gov/vuln/detail/CVE-2025-0416

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0417/

sev:HIGH 7.0 - CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/AU:Y/R:A/V:D/RE:L/U:Green

Lack of protection against brute force attacks in Valmet DNA visualization in DNA Operate. The possibility to make an arbitrary number of login attempts without any rate limit gives an attacker an increased chance of guessing passwords and then performing switching operations.

https://nvd.nist.gov/vuln/detail/CVE-2025-0417

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0418/

sev:MED 5.4 - CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/AU:N/R:A/V:D/RE:L/U:Green

Valmet DNA user passwords in plain text. This practice poses a security risk as attackers who gain access to local project data can read the passwords.

https://nvd.nist.gov/vuln/detail/CVE-2025-0418

NCSC Finland published some vulns in Valmet DNA, which is a DCS system. Those are always fun to attack and / or defend.

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0416/

sev:HIGH 8.9 - CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:N/AU:Y/R:U/V:D/RE:H/U:Amber

Local privilege escalation through insecure DCOM configuration in Valmet DNA versions prior to C2023. The DCOM object Valmet DNA Engineering has permissions that allow it to run commands as a user with the SeImpersonatePrivilege privilege. The SeImpersonatePrivilege privilege is a Windows permission that allows a process to impersonate another user. An attacker can use this vulnerability to escalate their privileges and take complete control of the system.

https://nvd.nist.gov/vuln/detail/CVE-2025-0416

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0417/

sev:HIGH 7.0 - CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/AU:Y/R:A/V:D/RE:L/U:Green

Lack of protection against brute force attacks in Valmet DNA visualization in DNA Operate. The possibility to make an arbitrary number of login attempts without any rate limit gives an attacker an increased chance of guessing passwords and then performing switching operations.

https://nvd.nist.gov/vuln/detail/CVE-2025-0417

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0418/

sev:MED 5.4 - CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/AU:N/R:A/V:D/RE:L/U:Green

Valmet DNA user passwords in plain text. This practice poses a security risk as attackers who gain access to local project data can read the passwords.

https://nvd.nist.gov/vuln/detail/CVE-2025-0418

NCSC Finland published some vulns in Valmet DNA, which is a DCS system. Those are always fun to attack and / or defend.

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0416/

sev:HIGH 8.9 - CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:N/AU:Y/R:U/V:D/RE:H/U:Amber

Local privilege escalation through insecure DCOM configuration in Valmet DNA versions prior to C2023. The DCOM object Valmet DNA Engineering has permissions that allow it to run commands as a user with the SeImpersonatePrivilege privilege. The SeImpersonatePrivilege privilege is a Windows permission that allows a process to impersonate another user. An attacker can use this vulnerability to escalate their privileges and take complete control of the system.

https://nvd.nist.gov/vuln/detail/CVE-2025-0416

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0417/

sev:HIGH 7.0 - CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/AU:Y/R:A/V:D/RE:L/U:Green

Lack of protection against brute force attacks in Valmet DNA visualization in DNA Operate. The possibility to make an arbitrary number of login attempts without any rate limit gives an attacker an increased chance of guessing passwords and then performing switching operations.

https://nvd.nist.gov/vuln/detail/CVE-2025-0417

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0418/

sev:MED 5.4 - CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/AU:N/R:A/V:D/RE:L/U:Green

Valmet DNA user passwords in plain text. This practice poses a security risk as attackers who gain access to local project data can read the passwords.

https://nvd.nist.gov/vuln/detail/CVE-2025-0418

NCSC Finland published some vulns in Valmet DNA, which is a DCS system. Those are always fun to attack and / or defend.

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0416/

sev:HIGH 8.9 - CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:N/AU:Y/R:U/V:D/RE:H/U:Amber

Local privilege escalation through insecure DCOM configuration in Valmet DNA versions prior to C2023. The DCOM object Valmet DNA Engineering has permissions that allow it to run commands as a user with the SeImpersonatePrivilege privilege. The SeImpersonatePrivilege privilege is a Windows permission that allows a process to impersonate another user. An attacker can use this vulnerability to escalate their privileges and take complete control of the system.

https://nvd.nist.gov/vuln/detail/CVE-2025-0416

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0417/

sev:HIGH 7.0 - CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/AU:Y/R:A/V:D/RE:L/U:Green

Lack of protection against brute force attacks in Valmet DNA visualization in DNA Operate. The possibility to make an arbitrary number of login attempts without any rate limit gives an attacker an increased chance of guessing passwords and then performing switching operations.

https://nvd.nist.gov/vuln/detail/CVE-2025-0417

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0418/

sev:MED 5.4 - CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/AU:N/R:A/V:D/RE:L/U:Green

Valmet DNA user passwords in plain text. This practice poses a security risk as attackers who gain access to local project data can read the passwords.

https://nvd.nist.gov/vuln/detail/CVE-2025-0418

NCSC Finland published some vulns in Valmet DNA, which is a DCS system. Those are always fun to attack and / or defend.

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0416/

sev:HIGH 8.9 - CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:N/AU:Y/R:U/V:D/RE:H/U:Amber

Local privilege escalation through insecure DCOM configuration in Valmet DNA versions prior to C2023. The DCOM object Valmet DNA Engineering has permissions that allow it to run commands as a user with the SeImpersonatePrivilege privilege. The SeImpersonatePrivilege privilege is a Windows permission that allows a process to impersonate another user. An attacker can use this vulnerability to escalate their privileges and take complete control of the system.

https://nvd.nist.gov/vuln/detail/CVE-2025-0416

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0417/

sev:HIGH 7.0 - CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/AU:Y/R:A/V:D/RE:L/U:Green

Lack of protection against brute force attacks in Valmet DNA visualization in DNA Operate. The possibility to make an arbitrary number of login attempts without any rate limit gives an attacker an increased chance of guessing passwords and then performing switching operations.

https://nvd.nist.gov/vuln/detail/CVE-2025-0417

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0418/

sev:MED 5.4 - CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/AU:N/R:A/V:D/RE:L/U:Green

Valmet DNA user passwords in plain text. This practice poses a security risk as attackers who gain access to local project data can read the passwords.

https://nvd.nist.gov/vuln/detail/CVE-2025-0418

NCSC Finland published some vulns in Valmet DNA, which is a DCS system. Those are always fun to attack and / or defend.

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0416/

sev:HIGH 8.9 - CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:N/AU:Y/R:U/V:D/RE:H/U:Amber

Local privilege escalation through insecure DCOM configuration in Valmet DNA versions prior to C2023. The DCOM object Valmet DNA Engineering has permissions that allow it to run commands as a user with the SeImpersonatePrivilege privilege. The SeImpersonatePrivilege privilege is a Windows permission that allows a process to impersonate another user. An attacker can use this vulnerability to escalate their privileges and take complete control of the system.

https://nvd.nist.gov/vuln/detail/CVE-2025-0416

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0417/

sev:HIGH 7.0 - CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/AU:Y/R:A/V:D/RE:L/U:Green

Lack of protection against brute force attacks in Valmet DNA visualization in DNA Operate. The possibility to make an arbitrary number of login attempts without any rate limit gives an attacker an increased chance of guessing passwords and then performing switching operations.

https://nvd.nist.gov/vuln/detail/CVE-2025-0417

https://www.valmet.com/about-us/about/research-and-development/vulnerabilityadvisories/cve-2025-0418/

sev:MED 5.4 - CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/AU:N/R:A/V:D/RE:L/U:Green

Valmet DNA user passwords in plain text. This practice poses a security risk as attackers who gain access to local project data can read the passwords.

https://nvd.nist.gov/vuln/detail/CVE-2025-0418

Microsoft:

Critical: Azure Health Bot Elevation of Privilege Vulnerability - CVE-2025-21384 https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21384

Critical: Azure Playwright Elevation of Privilege Vulnerability - CVE-2025-26683 https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-26683 @microsoftsec #cybersecurity #infosec #Azure

Another Microsoft cloud service vuln got patched. They claim no exploitation and it wasn't publicly known so you should be okay but that trust thing is hard.

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21384

sev:HIGH 8.3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

An authenticated attacker can exploit an Server-Side Request Forgery (SSRF) vulnerability in Microsoft Azure Health Bot to elevate privileges over a network.

https://nvd.nist.gov/vuln/detail/CVE-2025-21384

Microsoft:

Critical: Azure Health Bot Elevation of Privilege Vulnerability - CVE-2025-21384 https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21384

Critical: Azure Playwright Elevation of Privilege Vulnerability - CVE-2025-26683 https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-26683 @microsoftsec #cybersecurity #infosec #Azure

Another Microsoft cloud service vuln got patched. They claim no exploitation and it wasn't publicly known so you should be okay but that trust thing is hard.

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21384

sev:HIGH 8.3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

An authenticated attacker can exploit an Server-Side Request Forgery (SSRF) vulnerability in Microsoft Azure Health Bot to elevate privileges over a network.

https://nvd.nist.gov/vuln/detail/CVE-2025-21384

The CVE is published for this one. No CVSS yet though: https://nvd.nist.gov/vuln/detail/CVE-2025-30456

https://support.apple.com/en-us/122371

DiskArbitration

Available for: iPhone XS and later, iPad Pro 13-inch, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 7th generation and later, and iPad mini 5th generation and later

Impact: An app may be able to gain root privileges

Description: A parsing issue in the handling of directory paths was addressed with improved path validation.

CVE-2025-30456: Gergely Kalman (@gergely_kalman)

https://nvd.nist.gov/vuln/detail/CVE-2025-30456

#lazy #directoryTraversalMemes

Drupal published a bunch of CVEs for recent vulns of theirs, though they haven't been assessed for CVSS yet. I'm not going to list them all but there is one I want to point out.

https://www.drupal.org/security

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Drupal AI (Artificial Intelligence) allows OS Command Injection.This issue affects AI (Artificial Intelligence): from 0.0.0 before 1.0.5.

https://nvd.nist.gov/vuln/detail/CVE-2025-31693

Microsoft:

Critical: Azure Health Bot Elevation of Privilege Vulnerability - CVE-2025-21384 https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21384

Critical: Azure Playwright Elevation of Privilege Vulnerability - CVE-2025-26683 https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-26683 @microsoftsec #cybersecurity #infosec #Azure

Microsoft:

Critical: Azure Health Bot Elevation of Privilege Vulnerability - CVE-2025-21384 https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21384

Critical: Azure Playwright Elevation of Privilege Vulnerability - CVE-2025-26683 https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-26683 @microsoftsec #cybersecurity #infosec #Azure

Microsoft Azure Playwright EoP vuln.

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-26683

Improper authorization in Azure Playwright allows an unauthorized attacker to elevate privileges over a network.

Microsoft says that it is not publicly disclosed and not EITW so if it's really fixed, you should be good to go. But I would still take a look in your logs to see what you don't see.

Amazon, posted yesterday: Issue with AWS SAM CLI (CVE-2025-3047, CVE-2025-3048) has been resolved https://aws.amazon.com/security/security-bulletins/AWS-2025-008/ #Amazon #cybersecurity #Inffosec

Amazon, posted yesterday: Issue with AWS SAM CLI (CVE-2025-3047, CVE-2025-3048) has been resolved https://aws.amazon.com/security/security-bulletins/AWS-2025-008/ #Amazon #cybersecurity #Inffosec

Issue with AWS SAM CLI (CVE-2025-3047, CVE-2025-3048)

https://aws.amazon.com/security/security-bulletins/AWS-2025-008/

sev:MED 6.9 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

When running the AWS Serverless Application Model Command Line Interface (SAM CLI) build process with Docker and symlinks are included in the build files, the container environment allows a user to access privileged files on the host by leveraging the elevated permissions granted to the tool. A user could leverage the elevated permissions to access restricted files via symlinks and copy them to a more permissive location on the container. Users should upgrade to v1.133.0 or newer and ensure any forked or derivative code is patched to incorporate the new fixes.

https://nvd.nist.gov/vuln/detail/CVE-2025-3047

Amazon, posted yesterday: Issue with AWS SAM CLI (CVE-2025-3047, CVE-2025-3048) has been resolved https://aws.amazon.com/security/security-bulletins/AWS-2025-008/ #Amazon #cybersecurity #Inffosec

Amazon, posted yesterday: Issue with AWS SAM CLI (CVE-2025-3047, CVE-2025-3048) has been resolved https://aws.amazon.com/security/security-bulletins/AWS-2025-008/ #Amazon #cybersecurity #Inffosec

Issue with AWS SAM CLI (CVE-2025-3047, CVE-2025-3048)

https://aws.amazon.com/security/security-bulletins/AWS-2025-008/

sev:MED 6.9 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

When running the AWS Serverless Application Model Command Line Interface (SAM CLI) build process with Docker and symlinks are included in the build files, the container environment allows a user to access privileged files on the host by leveraging the elevated permissions granted to the tool. A user could leverage the elevated permissions to access restricted files via symlinks and copy them to a more permissive location on the container. Users should upgrade to v1.133.0 or newer and ensure any forked or derivative code is patched to incorporate the new fixes.

https://nvd.nist.gov/vuln/detail/CVE-2025-3047

Another old Fortinet advisory finally getting a CVE published. The advisory is from 2021, the CVE year is 2023, and here we are in 2025.

https://fortiguard.fortinet.com/psirt/FG-IR-21-023

sev:MED 4.5 - CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L/E:P/RL:U/RC:C

A buffer copy without checking size of input ('classic buffer overflow') in Fortinet FortiMail webmail and administrative interface version 6.4.0 through 6.4.4 and before 6.2.6 and FortiNDR administrative interface version 7.2.0 and before 7.1.0 allows an authenticated attacker with regular webmail access to trigger a buffer overflow and to possibly execute unauthorized code or commands via specifically crafted HTTP requests.

https://nvd.nist.gov/vuln/detail/CVE-2023-33302

Unraid with Tailscale is pretty popular so maybe go check your targets and / or assets.

https://docs.unraid.net/unraid-os/release-notes/7.0.1/

https://edac.dev/security/CVE-2025-29266/

sev:CRIT 9.6 - CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Unraid 7.0.0 before 7.0.1 allows remote users to access the Unraid WebGUI and web console as root without authentication if a container is running in Host networking mode with Use Tailscale enabled.

https://nvd.nist.gov/vuln/detail/CVE-2025-29266

CVE-2025-31160 Atop 2.11 heap problems

Link: https://openwall.com/lists/oss-security/2025/03/29/1
Discussion: https://news.ycombinator.com/item?id=43518560

CVE-2025-31160 Atop 2.11 heap problems
Link: https://openwall.com/lists/oss-security/2025/03/29/1
Comments: https://news.ycombinator.com/item?id=43518560

CVE-2025-31160 Atop 2.11 heap problems
https://openwall.com/lists/oss-security/2025/03/29/1
#ycombinator

CVE-2025-31160 Atop 2.11 heap problems

https://openwall.com/lists/oss-security/2025/03/29/1

#HackerNews #CVE-2025-31160 #heap #vulnerabilities #security #issues #OpenWall #OSS #security

Details about CVE-2025-31160 (memory corruption in #atop) are now available here: https://github.com/Atoptool/atop/issues/334

In a nutshell: atop at startup connects to local (non-privileged) TCP port 59123 where it expects certain data; if a regular user listens on that port, it can feed data to the next invocation of atop that can corrupt it.

The fix (https://github.com/Atoptool/atop/commit/542b7f7ac52926ca272129dba81d7db80279bb98) is primarily "don't do that" with some attempt at better parsing of the untrusted data (by adding return code checking of `sscanf`).

🚨CVE-2025-2071: OS Command Injection Vulnerability in FAST LTA Silent Brick WebUI

CVSS: 10

https://darkwebinformer.com/cve-2025-2071-os-command-injection-vulnerability-in-fast-lta-silent-brick-webui/

Canon CVE-2025-1268 Vulnerability: A Buffer Overflow Threatening Printer Security https://thecyberexpress.com/canon-printer-vulnerability-cve-2025-1268/ #outofboundsvulnerability #TheCyberExpressNews #Canonvulnerability #Vulnerabilities #TheCyberExpress #FirewallDaily #Canonprinter #CVE20251268 #GenericPlus #CyberNews

Here's another easy-mode PrivEsc like @wdormann was talking about the other day with his Nessus Agent CVE.

https://www.watchguard.com/wgrd-psirt/advisory/wgsa-2025-00004

sev:MED 6.3 - CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H

The WatchGuard Mobile VPN with SSL Client on Windows does not properly configure directory permissions when installed in a non-default directory. This could allow an authenticated local attacker to escalate to SYSTEM privileges on a vulnerable system. This issue affects Mobile VPN with SSL Client: from 11.0 through 12.11.

https://nvd.nist.gov/vuln/detail/CVE-2025-2781

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

Firefox developers reported CVE-2025-2857, a sandbox vulnerability similar to a zero-day reported this week in Google Chrome.

https://therecord.media/firefox-sandbox-vulnerability-similar-chrome-zero-day

Critical Firefox, Tor Browser sandbox escape flaw fixed (CVE-2025-2857)

https://www.helpnetsecurity.com/2025/03/28/critical-firefox-tor-browser-sandbox-escape-flaw-fixed-cve-2025-2857/

#Firefox #Tor

Critical Firefox, Tor Browser sandbox escape flaw fixed (CVE-2025-2857) https://www.helpnetsecurity.com/2025/03/28/critical-firefox-tor-browser-sandbox-escape-flaw-fixed-cve-2025-2857/ #securityupdate #vulnerability #Don'tmiss #Kaspersky #Hotstuff #Firefox #Chrome #Opera #News #Tor

Whoa, talk about déjà vu! Seems like Firefox is playing catch-up right after Chrome dropped a fix for a sandbox escape. 🤯 Keep an eye out for CVE-2025-2857.

So, what's the deal? In short, this nasty bug could let an attacker break right out of the browser's protective sandbox. And *that* means they could potentially gain full access to your system. Yeah, pretty scary stuff. 😱

If you're running Firefox on Windows, heads up! This affects versions 136.0.4, ESR 115.21.1, and ESR 128.8.1. This whole situation feels familiar because Chrome *just* patched CVE-2025-2783, a similar issue that attackers were already actively exploiting out in the wild!

Make no mistake, sandbox escapes are a huge deal. As a pentester, I can tell you: vulnerabilities like this get weaponized *fast*. Don't wait around.

Seriously, update your Firefox ASAP! Trust me, you don't want to deal with the fallout if someone exploits this. It could get costly, fast.

Ever seen a browser exploit do its thing live? Wild, right? Drop your stories below!

#infosec #pentesting #firefox #cybersecurity #updateNOW

Firefox 0-day security vulnerability (CVE-2025-2857) patched

Mozilla patches a sandbox escape vulnerability that is already being exploited (in Chrome)

:firefox:⁠https://www.mozilla.org/en-US/security/advisories/mfsa2025-19/

Announced: 2025-03-27
Impact: ⚠️ critical
Products: Firefox, Firefox ESR (Firefox on Windows only)
Fixed in:
• Firefox 136.0.4 :windows:
• Firefox ESR 115.21.1 :windows:
• Firefox ESR 128.8.1 :windows:

#Firefox #InfoSec #CVE #CVE_2025_2857

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

Way to go with CVE-2025-29927 Vercel...

Detect NetxJS CVE-2025-29927 efficiently and at scale https://www.patrowl.io/en/actualites/cve-2025-29927-next-js

Zscaler: CVE-2025-29927: Next.js Middleware Authorization Bypass Flaw https://www.zscaler.com/blogs/security-research/cve-2025-29927-next-js-middleware-authorization-bypass-flaw @threatlabz #cybersecurity #infosec

[Reproduce Steps]
Add Header

x-middleware-subrequest: middleware:middleware:middleware:middleware:middleware

to the request
⬇️
"Next.js POC for CVE-2025-29927"
👇
https://github.com/azu/nextjs-cve-2025-29927-poc

@da_667 Yes please. Rapid7 did publish this though: https://www.rapid7.com/blog/post/2025/03/25/etr-notable-vulnerabilities-in-next-js-cve-2025-29927/

It's not much, but it's better than the vendor.

I don't normally post JS stuff, but CVE-2025-29927 is a whole lot of fun!

"it was possible to skip running Middleware, which could allow requests to skip critical checks—such as authorization cookie validation—before reaching routes." 😱

https://nextjs.org/blog/cve-2025-29927

Get your Next.js updated!

I probably sound like a broken record at this point, but we're not sold yet on the world-ending nature of Next.js CVE-2025-29927.

The fact that the bug isn't known to have been successfully exploited in the wild despite the huge amount of media and industry attention it’s received sure feels like a reasonable early indicator that it's unlikely to be broadly exploitable (classic framework vuln), and may not have any easily identifiable remote attack vectors at all.

https://www.rapid7.com/blog/post/2025/03/25/etr-notable-vulnerabilities-in-next-js-cve-2025-29927/

Everyone’s talking about the Next.js vulnerability alert - and rightfully so. 👉 Here's why you need to detect and fix CVE-2025-29927 - now!

CVE-2025-29927 allows attackers to bypass crucial authorization checks via a simple header manipulation. This flaw affects a wide range of Next.js versions, potentially exposing sensitive data and critical admin functionalities.

Here's what you need to know:

👉 Impact: Attackers can gain unauthorized access to protected routes, leading to data breaches and privilege escalation.
👉 Vulnerable versions: Next.js 11.1.4 through 15.2.2.
👉 Detection: our Network Vulnerability Scanner now detects CVE-2025-29927, so a CVE-focused scan lets you identify vulnerable instances in your infrastructure - fast.

🔥 Don't wait for the exploit: act now

✅ Run a network scan

✅ Read the detailed write-up that explains how this vulnerability works, its impact, and detailed remediation steps ➡️ https://pentest-tools.com/blog/CVE-2025-29927-next-js-bypass

Next.js CVE-2025-29927 https://lobste.rs/s/l5c7gj #javascript #security #web
https://nextjs.org/blog/cve-2025-29927

CVE-2025-29927 Next.js Middleware Authorization Bypass Vulnerability  – Source: socprime.com https://ciso2ciso.com/cve-2025-29927-next-js-middleware-authorization-bypass-vulnerability-source-socprime-com/ #socprime.com #0CISO2CISO

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

Fortinet published another CVE for a vuln from 2019. Just something to keep in mind when people blame Fortinet shops when they get popped by unpatched vulns.

https://nvd.nist.gov/vuln/detail/CVE-2019-16149

Backdoor in a robot dog thing? Yes please.

https://takeonme.org/cves/cve-2025-2894/

sev:MED 6.6 - CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

The Go1 also known as "The World's First Intelligence Bionic Quadruped Robot Companion of Consumer Level," contains an undocumented backdoor that can enable the manufacturer, and anyone in possession of the correct API key, complete remote control over the affected robotic device using the CloudSail remote access service.

https://nvd.nist.gov/vuln/detail/CVE-2025-2894

🚨CVE-2025-24383: Dell Unity, Dell UnityVSA and Dell Unity XT remediation is available for multiple security vulnerabilities that could be exploited by malicious users to compromise the affected system

CVSS: 9.1

https://darkwebinformer.com/cve-2025-24383-dell-unity-dell-unityvsa-and-dell-unity-xt-remediation-is-available-for-multiple-security-vulnerabilities-that-could-be-exploited-by-malicious-users-to-compromise-the-aff/

Crypto vuln? In perl? That seems like something fedi is built to argue about.

https://metacpan.org/release/ZEFRAM/Data-Entropy-0.007/source/lib/Data/Entropy.pm#L80

Data::Entropy for Perl 0.007 and earlier use the rand() function as the default source of entropy, which is not cryptographically secure, for cryptographic functions.

https://nvd.nist.gov/vuln/detail/CVE-2025-1860

UAF PrivEsc in Exim. I think it was @buherator who shared the Openwall link for this earlier today or yesterday. It now has a CVE published.

https://www.exim.org/static/doc/security/CVE-2025-30232.txt

https://www.openwall.com/lists/oss-security/2025/03/26/1

sev:HIGH 8.1 - CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

A use-after-free in Exim 4.96 through 4.98.1 could allow users (with command-line access) to escalate privileges.

https://nvd.nist.gov/vuln/detail/CVE-2025-30232

wait3() system call as a side-channel in setuid programs (nvidia-modprobe CVE-2024-0149)

https://seclists.org/oss-sec/2025/q1/254

There are a bunch of CVEs for libming v0.4.0 ( it's a SWF output library ) published today. The issue for them was opened last month with PoCs, but once again, a project isn't using the Security page on its GitHub.

https://github.com/libming/libming/issues/330

https://nvd.nist.gov/vuln/detail/CVE-2025-29483

https://nvd.nist.gov/vuln/detail/CVE-2025-29484

https://nvd.nist.gov/vuln/detail/CVE-2025-29485

https://nvd.nist.gov/vuln/detail/CVE-2025-29486

https://nvd.nist.gov/vuln/detail/CVE-2025-29487

https://nvd.nist.gov/vuln/detail/CVE-2025-29488

https://nvd.nist.gov/vuln/detail/CVE-2025-29489

https://nvd.nist.gov/vuln/detail/CVE-2025-29490

https://nvd.nist.gov/vuln/detail/CVE-2025-29491

https://nvd.nist.gov/vuln/detail/CVE-2025-29492

https://nvd.nist.gov/vuln/detail/CVE-2025-29493

https://nvd.nist.gov/vuln/detail/CVE-2025-29494

https://nvd.nist.gov/vuln/detail/CVE-2025-29496

https://nvd.nist.gov/vuln/detail/CVE-2025-29497

Code injection in Apache Kylin.

https://lists.apache.org/thread/6j19pt8yoqfphf1lprtrzoqkvz1gwbnc

Improper Control of Generation of Code ('Code Injection') vulnerability in Apache Kylin.
If an attacker gets access to Kylin's system or project admin permission, the JDBC connection configuration maybe altered to execute arbitrary code from the remote. You are fine as long as the Kylin's system and project admin access is well protected.

This issue affects Apache Kylin: from 4.0.0 through 5.0.1.

Users are recommended to upgrade to version 5.0.2 or above, which fixes the issue.

https://nvd.nist.gov/vuln/detail/CVE-2025-30067

CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514: Frequently Asked Questions About IngressNightmare #SuggestedRead #devopsish https://www.tenable.com/blog/cve-2025-1974-frequently-asked-questions-about-ingressnightmare-kubernetes

Critical Kubernetes controller flaws: 4,000 IPs exposed, with patch urgency increasing due to code to exploit CVE-2025-1974 vulnerability being published https://www.databreachtoday.com/critical-kubernetes-controller-flaws-4000-ips-exposed-a-27868

Ingress-nginx CVE-2025-1974: What You Need to Know #SuggestedRead #devopsish https://kubernetes.io/blog/2025/03/24/ingress-nginx-cve-2025-1974/

🚨PoC Code to Exploit the IngressNightmare Vulnerabilities (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, and CVE-2025-1974)

https://darkwebinformer.com/poc-code-to-exploit-the-ingressnightmare-vulnerabilities-cve-2025-1097-cve-2025-1098-cve-2025-24514-and-cve-2025-1974/

CVE-2025-1974: Critical Set of Vulnerabilities in Ingress NGINX Controller for Kubernetes Leading to Unauthenticated RCE – Source: socprime.com https://ciso2ciso.com/cve-2025-1974-critical-set-of-vulnerabilities-in-ingress-nginx-controller-for-kubernetes-leading-to-unauthenticated-rce-source-socprime-com/ #rssfeedpostgeneratorecho #CyberSecurityNews #IngressNightmare #CVE-2025-1974 #Latestthreats #Vulnerability #socprimecom #socprime #Blog #CVE

Ingress-nginx CVE-2025-1974: What You Need to Know | Kubernetes https://kubernetes.io/blog/2025/03/24/ingress-nginx-cve-2025-1974/

CVE-2025-1974 #SuggestedRead #devopsish https://github.com/kubernetes/kubernetes/issues/131009

Jacob Sandum posted a detailed and well-written PoC for the IngressNightmare (CVE-2025-1974 ) vulnerability found in the Kubernetes ingress-nginx Admission Controller by Wiz (Woogle!). If you are looking for a quick way to reproduce the issue or validate detection and mitigation, take a look:
https://github.com/sandumjacob/IngressNightmare-POCs/blob/main/CVE-2025-1974/README.md

We will be performing an emergency upgrade of our cluster infrastructure to patch a series of critical security vulnerabilities (CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514) on our NGINX containers. As a result there may be a brief/intermittent disruption to Mastodon availability over the next hour. We apologize for the inconvenience, and hope you can quickly return to enjoying all the Nicole memes. Please see https://status.vmst.io for more information. #vmstio

Kubernetesでingress-nginx使ってる各位は確認しておいた方が良いかもです

Ingress-nginx CVE-2025-1974: What You Need to Know | Kubernetes : 👀
---
https://kubernetes.io/blog/2025/03/24/ingress-nginx-cve-2025-1974/

⚠️ Alerte sécurité sur Kubernetes : #IngressNightmare

Le 24 mars 2025, l’équipe de recherche de Wiz et les mainteneurs de Kubernetes ont dévoilé 5 vulnérabilités majeures affectant le très populaire Ingress-NGINX Controller (présent sur +40% des clusters).

Ces failles, dont la plus grave est CVE-2025-1974 (CVSS 9.8), permettent à un attaquant sans identifiants d’exécuter du code à distance (Remote Code Execution) et de prendre le contrôle complet du cluster Kubernetes, en accédant à tous les secrets (mots de passe, clés d’API, etc.).

Ce qui est en cause :
Le composant vulnérable est le Validating Admission Controller d’Ingress-NGINX. Il valide les objets "Ingress" mais est, par défaut, accessible sans authentification depuis le réseau interne du cluster – parfois même exposé publiquement.

Les chercheurs ont réussi à injecter des configurations NGINX malveillantes, puis à exécuter du code en important des bibliothèques à partir de fichiers temporaires via NGINX. Une véritable porte d’entrée invisible.

✅ Ce que vous devez faire rapidement:
Vérifiez si vous utilisez ingress-nginx :

kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx

Mettez à jour vers une version corrigée :

v1.12.1 ou v1.11.5

Si vous ne pouvez pas mettre à jour tout de suite :

Désactivez temporairement le webhook d’admission (voir instructions officielles).

[Sources officielles]
⬇️
Blog de recherche Wiz :
"IngressNightmare: 9.8 Critical Unauthenticated Remote Code Execution Vulnerabilities in Ingress NGINX"
👇
https://www.wiz.io/blog/ingress-nginx-kubernetes-vulnerabilities

📢 Annonce de Kubernetes (Security Response Committee) :
"Ingress-nginx CVE-2025-1974: What You Need to Know"
👇
https://kubernetes.io/blog/2025/03/24/ingress-nginx-cve-2025-1974/

#CyberVeille #Kubernetes #DevSecOps #CVE_2025_1974 #RCE

If you're running ingress-nginx in your Kubernetes cluster please take a look at this latest CVE details, it's a big one! Patches are out so please get updating as soon as you can!

https://kubernetes.io/blog/2025/03/24/ingress-nginx-cve-2025-1974/

#Kubernetes #Nginx #Ingress #CloudNative

CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514: Frequently Asked Questions About IngressNightmare – Source: securityboulevard.com https://ciso2ciso.com/cve-2025-1097-cve-2025-1098-cve-2025-1974-cve-2025-24513-cve-2025-24514-frequently-asked-questions-about-ingressnightmare-source-securityboulevard-com/ #rssfeedpostgeneratorecho #SecurityBloggersNetwork #CyberSecurityNews #SecurityBoulevard

Wow, things are getting wild in the Kubernetes world! The name alone – "IngressNightmare" – gives me chills! 🤯 It's crucial to know this affects the Ingress NGINX Controller, *not* the NGINX Ingress Controller. That's a big difference!

Wiz really uncovered something huge. We're talking over 6,500 vulnerable clusters, with the potential for some serious Remote Code Execution (RCE). Ouch! They found that a scary 43% of cloud environments are impacted.

It appears, that these kinds of vulnerabilities often slip past standard scans. You really need manual penetration testing to catch them. And as a pentester myself, I can tell you, it's frequently like digging for buried treasure! 😅

Here are the CVEs to watch out for: CVE-2025-24513, CVE-2025-24514, CVE-2025-1097, CVE-2025-1098, CVE-2025-1974. These have a CVSS score of 9.8! So, you'll want to update to 1.12.1, 1.11.5, or 1.10.7 *immediately*. Another crucial step? See if your Admission Webhook Endpoint is exposed. Make sure you're limiting access. Don't need it? Then, turn it off!

So, what are your experiences with K8s security? I'm curious, what tools do you swear by? 🤔

#kubernetes #security #pentesting #devsecops #cloudsecurity

CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514: Frequently Asked Questions About IngressNightmare #SuggestedRead #devopsish https://www.tenable.com/blog/cve-2025-1974-frequently-asked-questions-about-ingressnightmare-kubernetes

CVE-2025-24514 #SuggestedRead #devopsish https://github.com/kubernetes/kubernetes/issues/131006

🚨PoC Code to Exploit the IngressNightmare Vulnerabilities (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, and CVE-2025-1974)

https://darkwebinformer.com/poc-code-to-exploit-the-ingressnightmare-vulnerabilities-cve-2025-1097-cve-2025-1098-cve-2025-24514-and-cve-2025-1974/

oh, this ingress/nginx proxy vuln family: CVE-2025-1097, CVE-2025-1098, CVE-2025-24514

maybe we need to rewrite that component in rust? oh, wait.

We will be performing an emergency upgrade of our cluster infrastructure to patch a series of critical security vulnerabilities (CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514) on our NGINX containers. As a result there may be a brief/intermittent disruption to Mastodon availability over the next hour. We apologize for the inconvenience, and hope you can quickly return to enjoying all the Nicole memes. Please see https://status.vmst.io for more information. #vmstio

CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514: Frequently Asked Questions About IngressNightmare – Source: securityboulevard.com https://ciso2ciso.com/cve-2025-1097-cve-2025-1098-cve-2025-1974-cve-2025-24513-cve-2025-24514-frequently-asked-questions-about-ingressnightmare-source-securityboulevard-com/ #rssfeedpostgeneratorecho #SecurityBloggersNetwork #CyberSecurityNews #SecurityBoulevard

Wow, things are getting wild in the Kubernetes world! The name alone – "IngressNightmare" – gives me chills! 🤯 It's crucial to know this affects the Ingress NGINX Controller, *not* the NGINX Ingress Controller. That's a big difference!

Wiz really uncovered something huge. We're talking over 6,500 vulnerable clusters, with the potential for some serious Remote Code Execution (RCE). Ouch! They found that a scary 43% of cloud environments are impacted.

It appears, that these kinds of vulnerabilities often slip past standard scans. You really need manual penetration testing to catch them. And as a pentester myself, I can tell you, it's frequently like digging for buried treasure! 😅

Here are the CVEs to watch out for: CVE-2025-24513, CVE-2025-24514, CVE-2025-1097, CVE-2025-1098, CVE-2025-1974. These have a CVSS score of 9.8! So, you'll want to update to 1.12.1, 1.11.5, or 1.10.7 *immediately*. Another crucial step? See if your Admission Webhook Endpoint is exposed. Make sure you're limiting access. Don't need it? Then, turn it off!

So, what are your experiences with K8s security? I'm curious, what tools do you swear by? 🤔

#kubernetes #security #pentesting #devsecops #cloudsecurity

CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514: Frequently Asked Questions About IngressNightmare #SuggestedRead #devopsish https://www.tenable.com/blog/cve-2025-1974-frequently-asked-questions-about-ingressnightmare-kubernetes

🚨PoC Code to Exploit the IngressNightmare Vulnerabilities (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, and CVE-2025-1974)

https://darkwebinformer.com/poc-code-to-exploit-the-ingressnightmare-vulnerabilities-cve-2025-1097-cve-2025-1098-cve-2025-24514-and-cve-2025-1974/

CVE-2025-1097 #SuggestedRead #devopsish https://github.com/kubernetes/kubernetes/issues/131007

oh, this ingress/nginx proxy vuln family: CVE-2025-1097, CVE-2025-1098, CVE-2025-24514

maybe we need to rewrite that component in rust? oh, wait.

We will be performing an emergency upgrade of our cluster infrastructure to patch a series of critical security vulnerabilities (CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514) on our NGINX containers. As a result there may be a brief/intermittent disruption to Mastodon availability over the next hour. We apologize for the inconvenience, and hope you can quickly return to enjoying all the Nicole memes. Please see https://status.vmst.io for more information. #vmstio

CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514: Frequently Asked Questions About IngressNightmare – Source: securityboulevard.com https://ciso2ciso.com/cve-2025-1097-cve-2025-1098-cve-2025-1974-cve-2025-24513-cve-2025-24514-frequently-asked-questions-about-ingressnightmare-source-securityboulevard-com/ #rssfeedpostgeneratorecho #SecurityBloggersNetwork #CyberSecurityNews #SecurityBoulevard

Wow, things are getting wild in the Kubernetes world! The name alone – "IngressNightmare" – gives me chills! 🤯 It's crucial to know this affects the Ingress NGINX Controller, *not* the NGINX Ingress Controller. That's a big difference!

Wiz really uncovered something huge. We're talking over 6,500 vulnerable clusters, with the potential for some serious Remote Code Execution (RCE). Ouch! They found that a scary 43% of cloud environments are impacted.

It appears, that these kinds of vulnerabilities often slip past standard scans. You really need manual penetration testing to catch them. And as a pentester myself, I can tell you, it's frequently like digging for buried treasure! 😅

Here are the CVEs to watch out for: CVE-2025-24513, CVE-2025-24514, CVE-2025-1097, CVE-2025-1098, CVE-2025-1974. These have a CVSS score of 9.8! So, you'll want to update to 1.12.1, 1.11.5, or 1.10.7 *immediately*. Another crucial step? See if your Admission Webhook Endpoint is exposed. Make sure you're limiting access. Don't need it? Then, turn it off!

So, what are your experiences with K8s security? I'm curious, what tools do you swear by? 🤔

#kubernetes #security #pentesting #devsecops #cloudsecurity

CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514: Frequently Asked Questions About IngressNightmare #SuggestedRead #devopsish https://www.tenable.com/blog/cve-2025-1974-frequently-asked-questions-about-ingressnightmare-kubernetes

CVE-2025-24513 #SuggestedRead #devopsish https://github.com/kubernetes/kubernetes/issues/131005

We will be performing an emergency upgrade of our cluster infrastructure to patch a series of critical security vulnerabilities (CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514) on our NGINX containers. As a result there may be a brief/intermittent disruption to Mastodon availability over the next hour. We apologize for the inconvenience, and hope you can quickly return to enjoying all the Nicole memes. Please see https://status.vmst.io for more information. #vmstio

CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514: Frequently Asked Questions About IngressNightmare – Source: securityboulevard.com https://ciso2ciso.com/cve-2025-1097-cve-2025-1098-cve-2025-1974-cve-2025-24513-cve-2025-24514-frequently-asked-questions-about-ingressnightmare-source-securityboulevard-com/ #rssfeedpostgeneratorecho #SecurityBloggersNetwork #CyberSecurityNews #SecurityBoulevard

Wow, things are getting wild in the Kubernetes world! The name alone – "IngressNightmare" – gives me chills! 🤯 It's crucial to know this affects the Ingress NGINX Controller, *not* the NGINX Ingress Controller. That's a big difference!

Wiz really uncovered something huge. We're talking over 6,500 vulnerable clusters, with the potential for some serious Remote Code Execution (RCE). Ouch! They found that a scary 43% of cloud environments are impacted.

It appears, that these kinds of vulnerabilities often slip past standard scans. You really need manual penetration testing to catch them. And as a pentester myself, I can tell you, it's frequently like digging for buried treasure! 😅

Here are the CVEs to watch out for: CVE-2025-24513, CVE-2025-24514, CVE-2025-1097, CVE-2025-1098, CVE-2025-1974. These have a CVSS score of 9.8! So, you'll want to update to 1.12.1, 1.11.5, or 1.10.7 *immediately*. Another crucial step? See if your Admission Webhook Endpoint is exposed. Make sure you're limiting access. Don't need it? Then, turn it off!

So, what are your experiences with K8s security? I'm curious, what tools do you swear by? 🤔

#kubernetes #security #pentesting #devsecops #cloudsecurity

CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514: Frequently Asked Questions About IngressNightmare #SuggestedRead #devopsish https://www.tenable.com/blog/cve-2025-1974-frequently-asked-questions-about-ingressnightmare-kubernetes

CVE-2025-1098 #SuggestedRead #devopsish https://github.com/kubernetes/kubernetes/issues/131008

🚨PoC Code to Exploit the IngressNightmare Vulnerabilities (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, and CVE-2025-1974)

https://darkwebinformer.com/poc-code-to-exploit-the-ingressnightmare-vulnerabilities-cve-2025-1097-cve-2025-1098-cve-2025-24514-and-cve-2025-1974/

oh, this ingress/nginx proxy vuln family: CVE-2025-1097, CVE-2025-1098, CVE-2025-24514

maybe we need to rewrite that component in rust? oh, wait.

We will be performing an emergency upgrade of our cluster infrastructure to patch a series of critical security vulnerabilities (CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514) on our NGINX containers. As a result there may be a brief/intermittent disruption to Mastodon availability over the next hour. We apologize for the inconvenience, and hope you can quickly return to enjoying all the Nicole memes. Please see https://status.vmst.io for more information. #vmstio

CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24513, CVE-2025-24514: Frequently Asked Questions About IngressNightmare – Source: securityboulevard.com https://ciso2ciso.com/cve-2025-1097-cve-2025-1098-cve-2025-1974-cve-2025-24513-cve-2025-24514-frequently-asked-questions-about-ingressnightmare-source-securityboulevard-com/ #rssfeedpostgeneratorecho #SecurityBloggersNetwork #CyberSecurityNews #SecurityBoulevard

Wow, things are getting wild in the Kubernetes world! The name alone – "IngressNightmare" – gives me chills! 🤯 It's crucial to know this affects the Ingress NGINX Controller, *not* the NGINX Ingress Controller. That's a big difference!

Wiz really uncovered something huge. We're talking over 6,500 vulnerable clusters, with the potential for some serious Remote Code Execution (RCE). Ouch! They found that a scary 43% of cloud environments are impacted.

It appears, that these kinds of vulnerabilities often slip past standard scans. You really need manual penetration testing to catch them. And as a pentester myself, I can tell you, it's frequently like digging for buried treasure! 😅

Here are the CVEs to watch out for: CVE-2025-24513, CVE-2025-24514, CVE-2025-1097, CVE-2025-1098, CVE-2025-1974. These have a CVSS score of 9.8! So, you'll want to update to 1.12.1, 1.11.5, or 1.10.7 *immediately*. Another crucial step? See if your Admission Webhook Endpoint is exposed. Make sure you're limiting access. Don't need it? Then, turn it off!

So, what are your experiences with K8s security? I'm curious, what tools do you swear by? 🤔

#kubernetes #security #pentesting #devsecops #cloudsecurity

🚨CVE-2024-42533: SQL Injection in StandVoice by Convivance

https://darkwebinformer.com/cve-2024-42533-sql-injection-in-standvoice-by-convivance/

That RCE in Appsmith from December has a write-up.

https://rhinosecuritylabs.com/research/cve-2024-55963-unauthenticated-rce-in-appsmith/

https://github.com/appsmithorg/appsmith/releases/tag/v1.52

While reviewing the Appsmith Enterprise platform, Rhino Security Labs uncovered a series of critical vulnerabilities affecting default installations of the product. Most severe among them is CVE-2024-55963, which allows unauthenticated remote code execution due to a misconfigured PostgreSQL database included by default. Two additional vulnerabilities (CVE-2024-55964 and CVE-2024-55965) enable unauthorized access to sensitive data and application denial of service.

Unfortunately, the CVE still isn't in NVD.

https://nvd.nist.gov/vuln/detail/CVE-2024-55963

Multiple CVEs in gnuplot. They are all sev:MED 6.2.

https://access.redhat.com/security/cve/CVE-2025-31176

https://access.redhat.com/security/cve/CVE-2025-31178

https://access.redhat.com/security/cve/CVE-2025-31179

https://access.redhat.com/security/cve/CVE-2025-31180

https://access.redhat.com/security/cve/CVE-2025-31181

Multiple CVEs in gnuplot. They are all sev:MED 6.2.

https://access.redhat.com/security/cve/CVE-2025-31176

https://access.redhat.com/security/cve/CVE-2025-31178

https://access.redhat.com/security/cve/CVE-2025-31179

https://access.redhat.com/security/cve/CVE-2025-31180

https://access.redhat.com/security/cve/CVE-2025-31181

Multiple CVEs in gnuplot. They are all sev:MED 6.2.

https://access.redhat.com/security/cve/CVE-2025-31176

https://access.redhat.com/security/cve/CVE-2025-31178

https://access.redhat.com/security/cve/CVE-2025-31179

https://access.redhat.com/security/cve/CVE-2025-31180

https://access.redhat.com/security/cve/CVE-2025-31181

Multiple CVEs in gnuplot. They are all sev:MED 6.2.

https://access.redhat.com/security/cve/CVE-2025-31176

https://access.redhat.com/security/cve/CVE-2025-31178

https://access.redhat.com/security/cve/CVE-2025-31179

https://access.redhat.com/security/cve/CVE-2025-31180

https://access.redhat.com/security/cve/CVE-2025-31181

Multiple CVEs in gnuplot. They are all sev:MED 6.2.

https://access.redhat.com/security/cve/CVE-2025-31176

https://access.redhat.com/security/cve/CVE-2025-31178

https://access.redhat.com/security/cve/CVE-2025-31179

https://access.redhat.com/security/cve/CVE-2025-31180

https://access.redhat.com/security/cve/CVE-2025-31181

Active exploitation of critical SAP flaw CVE-2017-12637 reported by Onapsis
#cybersecurity #infosec #attack #activeexploit
https://beyondmachines.net/event_details/active-exploitation-of-critical-sap-flaw-cve-2017-12637-reported-by-onapsis-3-q-e-2-a/gD2P6Ple2L

Patchez Google Chrome : cette faille zero-day est exploitée par une campagne d’espionnage https://www.it-connect.fr/google-chrome-faille-zero-day-est-exploitee-campagne-espionnage-cve-2025-2783/ #ActuCybersécurité #Cybersécurité #Vulnérabilité #Google

Whoa, talk about déjà vu! Seems like Firefox is playing catch-up right after Chrome dropped a fix for a sandbox escape. 🤯 Keep an eye out for CVE-2025-2857.

So, what's the deal? In short, this nasty bug could let an attacker break right out of the browser's protective sandbox. And *that* means they could potentially gain full access to your system. Yeah, pretty scary stuff. 😱

If you're running Firefox on Windows, heads up! This affects versions 136.0.4, ESR 115.21.1, and ESR 128.8.1. This whole situation feels familiar because Chrome *just* patched CVE-2025-2783, a similar issue that attackers were already actively exploiting out in the wild!

Make no mistake, sandbox escapes are a huge deal. As a pentester, I can tell you: vulnerabilities like this get weaponized *fast*. Don't wait around.

Seriously, update your Firefox ASAP! Trust me, you don't want to deal with the fallout if someone exploits this. It could get costly, fast.

Ever seen a browser exploit do its thing live? Wild, right? Drop your stories below!

#infosec #pentesting #firefox #cybersecurity #updateNOW

CVE ID: CVE-2025-2783
Vendor: Google
Product: Chromium Mojo
Date Added: 2025-03-27
Vulnerability: Google Chromium Mojo Sandbox Escape Vulnerability
Notes: https://chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop_25.html ; https://nvd.nist.gov/vuln/detail/CVE-2025-2783
CVE URL: https://nvd.nist.gov/vuln/detail/CVE-2025-2783

New: CISA has updated the KEV catalogue.

- CVE-2025-2783: Google Chromium Mojo Sandbox Escape Vulnerability https://www.cve.org/CVERecord?id=CVE-2025-2783

- Added yesterday:

- CVE-2019-9874: Sitecore CMS and Experience Platform (XP) Deserialization Vulnerability https://www.cve.org/CVERecord?id=CVE-2019-9874

- CVE-2019-9875: Sitecore CMS and Experience Platform (XP) Deserialization Vulnerability https://www.cve.org/CVERecord?id=CVE-2019-9875 #CISA #cybersecurity #infosec #Google

Microsoft's notes for Edge Security Updates, posted yesterday: https://msrc.microsoft.com/update-guide

Chromium: CVE-2025-2783 Incorrect handle provided in unspecified circumstances in Mojo on Windows https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-2783 @microsoftsec #Microsoft #cybersecurity #Infosec #Windows

This update included the fix for CVE-2025-2783.

Just to be 100% clear this update included the fix for CVE-2025-2783. We actually had that out in the previous build 7.2.3621.71 from yesterday.

Just to be 100% clear this update included the fix for CVE-2025-2783. We actually had that out in the previous build 7.2.3621.71 from yesterday.

Just to be 100% clear this update included the fix for CVE-2025-2783. Indeed we were the first non-Chrome browser to get that out.

The CVE for this is published but no CVSS assessment yet: https://nvd.nist.gov/vuln/detail/CVE-2025-2783

If you missed this.

Security Week: Google Has Patched CVE-2025-2783, the Chrome Sandbox Escape Zero-Day Vulnerability Caught by Kaspersky https://www.securityweek.com/google-patches-chrome-sandbox-escape-zero-day-caught-by-kaspersky/ @SecurityWeek #cybersecurity #Infosec #Google #Chrome

Google fixes exploited Chrome sandbox bypass zero-day (CVE-2025-2783) – Help Net Security https://www.macken.xyz/2025/03/google-fixes-exploited-chrome-sandbox-bypass-zero-day-cve-2025-2783-help-net-security/?utm_source=dlvr.it&utm_medium=mastodon

The vulnerability, tracked as CVE-2025-2783, was chained with a second exploit for remote code execution in attacks targeting organizations in Russia. https://www.securityweek.com/google-patches-chrome-sandbox-escape-zero-day-caught-by-kaspersky/

Google fixes exploited Chrome sandbox bypass zero-day (CVE-2025-2783) https://www.helpnetsecurity.com/2025/03/26/google-fixes-exploited-chrome-sandbox-bypass-zero-day-cve-2025-2783/ #Don'tmiss #Kaspersky #Hotstuff #exploit #Windows #Chrome #0-day #News #APT

Chrome Releases Critical Update to Address CVE-2025-2783 Vulnerability https://thecyberexpress.com/chrome-stable-channel-update/ #StableChannelUpdate #TheCyberExpressNews #Vulnerabilities #TheCyberExpress #FirewallDaily #CVE20252783 #CyberNews #Windows

Chrome *again*? 🙄 Looks like Google's patching *another* critical flaw (CVE-2025-2783), and yep, attackers are already exploiting it in the wild.

Heads up, Windows users – you're the main target, with Russian orgs specifically in the crosshairs. 🇷🇺 The vulnerability's lurking in Mojo (Chrome's Inter-Process Communication system). And get this: all it takes is a convincing phishing email. 🎣 Someone clicks the link, and bam – their system's compromised.

What's really nasty? It cleverly gets around the Chrome sandbox. 🤯 Kaspersky's already tracking this, calling it 'Operation ForumTroll' and linking it to an APT group. Speaking as a pentester, trust me, finding vulnerabilities this deep isn't easy. Your run-of-the-mill scans just won't cut it here.

So, what's the game plan?
1. Update Chrome NOW! Like, right now. 🚨
2. Seriously, double down on training your staff about phishing threats.
3. Keep a close eye on your systems – think SIEM/EDR monitoring.

Curious to know, what are your go-to tools for hunting down threats like this? And how are you folks bracing yourselves against these advanced attacks? 🤔

Stay safe out there! ✌️

#Security #Chrome #Pentest #APT

EITW in Chrome if that's the kind of thing you care about: https://chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop_25.html

Google is aware of reports that an exploit for CVE-2025-2783 exists in the wild.

Bizerba doing that thing like in school where you take up as much of the page as possible. Instead of DoS they say:

An authenticated attacker can compromise the availability of the device via the network

https://www.bizerba.com/downloads/global/information-security/2025/bizerba-sa-2025-0002.pdf

Through the public FTP access the mass storage can be completely filled by mass uploading of data because no quota is in place.

sev:MED 6.5 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

https://nvd.nist.gov/vuln/detail/CVE-2025-2820

Service desk application vulns are always fun. I don't know how popular OXARI is, but if you know it, you might want to look into this one.

https://cert.pl/en/posts/2025/03/CVE-2025-1542/

sev:CRIT 9.3 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Improper permission control vulnerability in the OXARI ServiceDesk application could allow an attacker using a guest access or an unprivileged account to gain additional administrative permissions in the application.This issue affects OXARI ServiceDesk in versions before 2.0.324.0.

https://nvd.nist.gov/vuln/detail/CVE-2025-1542

I don't know how popular Pagure is but this RCE via git seems like it's worth patching. Or attacking. No judgement.

https://access.redhat.com/security/cve/CVE-2024-47516

sev:CRIT 9.8 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

A vulnerability was found in Pagure. An argument injection in Git during retrieval of the repository history leads to remote code execution on the Pagure instance.

https://nvd.nist.gov/vuln/detail/CVE-2024-47516

Apache Camel Exploit Attempt by Vulnerability Scan (CVE-2025-27636, CVE-2025-29891) https://isc.sans.edu/diary/31814

Authentication bypass CVE-2025-22230 impacts VMware Windows Tools – Source: securityaffairs.com https://ciso2ciso.com/authentication-bypass-cve-2025-22230-impacts-vmware-windows-tools-source-securityaffairs-com/ #rssfeedpostgeneratorecho #informationsecuritynews #ITInformationSecurity #SecurityAffairscom #CyberSecurityNews #PierluigiPaganini #SecurityAffairs #SecurityAffairs #BreakingNews #SecurityNews #hackingnews #vmwaretools #Security #hacking

VMware corrige une faille importante dans les VMware Tools pour Windows : CVE-2025-22230 https://www.it-connect.fr/vmware-corrige-une-faille-vmware-tools-pour-windows-cve-2025-22230/ #ActuCybersécurité #Cybersécurité #Vulnérabilité #Windows #VMware

VMware corrige une faille importante dans les VMware Tools pour Windows : CVE-2025-22230 https://www.it-connect.fr/vmware-corrige-une-faille-vmware-tools-pour-windows-cve-2025-22230/ #ActuCybersécurité #Cybersécurité #Vulnérabilité #Windows #VMware

Seriously, Broadcom... what's the deal lately? 🤯

First up, we've got CVE-2025-22230 hitting VMware Tools for Windows. This nasty bug basically lets standard users inside a VM escalate their privileges to admin level. Yikes! 😬 With a CVSS score of 7.8, you'll want to jump on this fix ASAP. It impacts versions 11.x.x and 12.x.x, so upgrading to 12.5.1 needs to be right at the top of your list!

But wait, there's more. CrushFTP is also sounding the alarm about unauthenticated access vulnerabilities lurking on HTTP(S) ports in versions 10 and 11. It's definitely time to double-check those DMZ configurations. Rapid7 has confirmed that exploits are out there, allowing unauthorized access. Pretty intense, right?

Stuff like this is a stark reminder: while automated scans have their place, they just don't cut it alone. Real-deal penetration testing is absolutely essential. Those manual checks are what uncover the sneaky issues that automated tools often breeze right past.

What's your take on this recent wave? How are you keeping your own environments locked down tight? Let's talk 👇

#ITSecurity #Pentesting #VMware #Cybersecurity #InfoSec #VulnerabilityManagement

A new twist on #ESXicape - you need local admin rights to escape the VM to the hypervisor, right?

Slight issue - VMware Tools, installed inside VMs, allows local user to local admin privilege escalation on every VM due to vuln CVE-2025-22230

“A malicious actor with non-administrative privileges on a Windows guest VM may gain ability to perform certain high-privilege operations within that VM.”

Discovered by Positive Technologies, who US claim hack for Moscow.

https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/25518

Auth bypass vuln in VMWare Tools for Windows. Nice.

https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/25518

sev:HIGH 7.8 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

VMware Tools for Windows contains an authentication bypass vulnerability due to improper access control. A malicious actor with non-administrative privileges on a guest VM may gain ability to perform certain high privilege operations within that VM.

https://nvd.nist.gov/vuln/detail/CVE-2025-22230

Multiple Denial-of-Service vulnerabilities in Hitachi Energy’s RTU500 series Product

This includes a couple sev:HIGH CVEs. Normally DoS vulns bore me, but when they're in RTUs used in energy, they get more interesting.

https://publisher.hitachienergy.com/preview?DocumentId=8DBD000207&languageCode=en&Preview=true

CVE-2024-10037
CVE-2024-11499
CVE-2024-12169
CVE-2025-1445

Multiple Denial-of-Service vulnerabilities in Hitachi Energy’s RTU500 series Product

This includes a couple sev:HIGH CVEs. Normally DoS vulns bore me, but when they're in RTUs used in energy, they get more interesting.

https://publisher.hitachienergy.com/preview?DocumentId=8DBD000207&languageCode=en&Preview=true

CVE-2024-10037
CVE-2024-11499
CVE-2024-12169
CVE-2025-1445

Multiple Denial-of-Service vulnerabilities in Hitachi Energy’s RTU500 series Product

This includes a couple sev:HIGH CVEs. Normally DoS vulns bore me, but when they're in RTUs used in energy, they get more interesting.

https://publisher.hitachienergy.com/preview?DocumentId=8DBD000207&languageCode=en&Preview=true

CVE-2024-10037
CVE-2024-11499
CVE-2024-12169
CVE-2025-1445

Multiple Denial-of-Service vulnerabilities in Hitachi Energy’s RTU500 series Product

This includes a couple sev:HIGH CVEs. Normally DoS vulns bore me, but when they're in RTUs used in energy, they get more interesting.

https://publisher.hitachienergy.com/preview?DocumentId=8DBD000207&languageCode=en&Preview=true

CVE-2024-10037
CVE-2024-11499
CVE-2024-12169
CVE-2025-1445

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

Looks like ABB published 13 CVEs for B&R APROL <4.4-01, including at least one sev:CRIT code injection vuln.

https://www.br-automation.com/fileadmin/SA24P015-77573c08.pdf

CVE-2024-45482, CVE-2024-45481, CVE-2024-45480, CVE-2024-8315, CVE-2024-45484, CVE-2024-45483, CVE-2024-8313, CVE-2024-8314, CVE-2024-10206, CVE-2024-10207, CVE-2024-10208, CVE-2024-10210, CVE-2024-10209

SnapCenter Security Flaw Rated Critical—NetApp Urges Immediate Patch https://thecyberexpress.com/netapp-snapcenter-vulnerability-cve-2025-26512/ #NetAppVulnerability #TheCyberExpressNews #SnapCenterServer #Vulnerabilities #TheCyberExpress #FirewallDaily #CVE202526512 #SnapCenter #CyberNews

WatchTower: XSS To RCE By Abusing Custom File Handlers - Kentico Xperience CMS (CVE-2025-2748) https://labs.watchtowr.com/xss-to-rce-by-abusing-custom-file-handlers-kentico-xperience-cms-cve-2025-2748/ #cybersecurity #infosec

I know that many of us tend to scoff at XSS vulns, but it's good to be reminded how they can be successfully used in a chain for something more interesting.

https://labs.watchtowr.com/xss-to-rce-by-abusing-custom-file-handlers-kentico-xperience-cms-cve-2025-2748/

WatchTower: XSS To RCE By Abusing Custom File Handlers - Kentico Xperience CMS (CVE-2025-2748) https://labs.watchtowr.com/xss-to-rce-by-abusing-custom-file-handlers-kentico-xperience-cms-cve-2025-2748/ #cybersecurity #infosec

I know that many of us tend to scoff at XSS vulns, but it's good to be reminded how they can be successfully used in a chain for something more interesting.

https://labs.watchtowr.com/xss-to-rce-by-abusing-custom-file-handlers-kentico-xperience-cms-cve-2025-2748/

XSS To RCE By Abusing Custom File Handlers - Kentico Xperience CMS (CVE-2025-2748) - watchTowr Labs https://labs.watchtowr.com/xss-to-rce-by-abusing-custom-file-handlers-kentico-xperience-cms-cve-2025-2748/

CVE-2025-27407: Inside the Critical GraphQL-Ruby RCE Vulnerability https://cenobe.com/blog/cve-2025-27407/

This has been a busy month for Malcolm! I pushed hard to get v25.03.0 out earlier this month, as it contained pretty much just the Keycloak integration one of our partners (and major funding sources) was waiting for. Rather than wait until April for the other stuff that would have gone into the regular end-of-the-month release, I decided to pull those items into this smaller release just a week and a half after the last one.

Malcolm v25.03.1 contains a few enhancements, bug fixes, and several component version updates, including one that addresses a CVE that may affect Hedgehog Linux Kiosk mode and Malcolm's API container.

NOTE: If you have not already upgraded to v25.03.0, read the notes for v25.02.0 and v25.03.0 and follow the Read Before Upgrading instructions on those releases.

Changes in this release

• ✨ Features and enhancements
  • Incorporate new S7comm device identification log, s7comm_known_devices.log (#622)
  • Display current PCAP, Zeek, and Suricata capture results in Hedgehog Linux Kiosk mode (#566)
  • Keycloak authentication: configurable group or role membership restrictions for login (#633) (see Requiring user groups and realm roles)
  • Mark newly-discovered and uninventoried devices in logs during NetBox enrichment (#573)
  • Added "Apply recommended system tweaks automatically without asking for confirmation?" question to install.py to allow the user to accept changes to sysctl.conf, grub kernel parameters, etc., without having to answer "yes" to each one.
• ✅ Component version updates
  • Arkime to v5.6.2
  • evtx to v0.9.0
  • Fluent Bit to v3.2.10
  • gunicorn to v23.0.0 to address CVE-2024-6827, "Gunicorn HTTP Request/Response Smuggling vulnerability"
  • Zeek to v7.1.1
• 🐛 Bug fixes
  • Fix install.py error when answering yes to "Pull Malcolm images?" with podman (#604)
  • Order of user-provided tags from PCAP upload interface not preserved (#624)
• 📄 Configuration changes (in environment variables in ./config/) for Malcolm and in control_vars.conf for Hedgehog Linux
  • added NGINX_REQUIRE_GROUP and NGINX_REQUIRE_ROLE to auth-common.env to support Requiring user groups and realm roles for Keycloak authentication
• 🧹 Code and project maintenance
  • Ensure Malcolm's NetBox configuration Python scripts are baked into the image in addition to bind-mounting them in docker-compose.yml at runtime.

Malcolm is a powerful, easily deployable network 🖧 traffic analysis tool suite for network security monitoring 🕵🏻‍♀️.

Malcolm operates as a cluster of containers 📦, isolated sandboxes which each serve a dedicated function of the system. This makes Malcolm deployable with frameworks like Docker 🐋, Podman 🦭, and Kubernetes ⎈. Check out the Quick Start guide for examples on how to get up and running.

Alternatively, dedicated official ISO installer images 💿 for Malcolm and Hedgehog Linux 🦔 can be downloaded from Malcolm's releases page on GitHub. Due to limits on individual files in GitHub releases, these ISO files have been split 🪓 into 2GB chunks and can be reassembled with scripts provided for both Bash 🐧 (release_cleaver.sh) and PowerShell 🪟 (release_cleaver.ps1). See Downloading Malcolm - Installer ISOs for instructions.

As always, join us on the Malcolm discussions board 💬 to engage with the community, or pop some corn 🍿 and watch a video 📼.

#Malcolm #HedgehogLinux #Zeek #Arkime #NetBox #OpenSearch #Elasticsearch #Suricata #SSO #OIDC #Keycloak #PCAP #NetworkTrafficAnalysis #networksecuritymonitoring #OT #ICS #icssecurity #CyberSecurity #Cyber #Infosec #INL #DHS #CISA #CISAgov

📣 EMERGENCY UPDATES 📣

Apple pushed additional updates for 3 zero-days that may have been actively exploited.

🐛 CVE-2025-24200 (Accessibility) additional patches,
🐛 CVE-2025-24201 (WebKit) additional patches:
- iOS and iPadOS 15.8.4
- iOS and iPadOS 16.7.11

🐛 CVE-2025-24085 (CoreMedia) additional patches:
- iPadOS 17.7.6
- macOS Sonoma 14.7.5
- macOS Ventura 13.7.5

#apple #cybersecurity #infosec #security #ios

CVE-2024-9956 - PassKey Account Takeover in All Mobile Browsers: https://mastersplinter.work/research/passkey/