Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-34491PUBLISHED: 2022-06-25
In the RSS extension for MediaWiki through 1.38.1, when the $wgRSSAllowLinkTag config variable was set to true, and a new RSS feed was created with certain XSS payloads within its description tags and added to the $wgRSSUrlWhitelist config variable, stored XSS could occur via MediaWiki's template sy...
CVE-2022-29931PUBLISHED: 2022-06-25Raytion 7.2.0 allows reflected Cross-site Scripting (XSS).
CVE-2022-31017PUBLISHED: 2022-06-25
Zulip is an open-source team collaboration tool. Versions 2.1.0 through and including 5.2 are vulnerable to a logic error. A stream configured as private with protected history, where new subscribers should not be allowed to see messages sent before they were subscribed, when edited causes the serve...
CVE-2022-31016PUBLISHED: 2022-06-25
Argo CD is a declarative continuous deployment for Kubernetes. Argo CD versions v0.7.0 and later are vulnerable to an uncontrolled memory consumption bug, allowing an authorized malicious user to crash the repo-server service, resulting in a Denial of Service. The attacker must be an authenticated A...
CVE-2022-24893PUBLISHED: 2022-06-25
ESP-IDF is the official development framework for Espressif SoCs. In Espressif’s Bluetooth Mesh SDK (`ESP-BLE-MESH`), a memory corruption vulnerability can be triggered during provisioning, because there is no check for the `SegN` field of the Transaction Start PDU. This can resul...
User Rank: Apprentice
9/10/2018 | 6:02:37 PM
Some caveats worth mentioning: new buyers of security automation products may find themselves experiencing sticker shock or falling victim to a still-maturing product space. Many vendor products are prohibitively expensive to the organizations that might benefit most (i.e., the long tail) and too often lock-in users with proprietary workflow formats. That said, automation is worth exploring—and perhaps adopting—for many organizations. My organization has realized numerous benefits to date.
An additional note of caution: I see many organizations rushing to automate workflows without first running the numbers; and, while automation has many benefits, it is first and foremost a matter of economics. Deciding what could, should, and will be slated for automation is an issue of resource management and optimization, whether those resources are people hours, pay-by-use cloud services, or particular team members with in-demand skills and limited availability.
Finally, organizations new to automation need to recognize that deploying new automation workflows is, in many ways, similar to deploying a new "product"—in that the workflows may (in more ways than expected) require additional support resources and know-how for testing, monitoring, and maintenance.