Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-23119PUBLISHED: 2023-02-02
The use of the cyclic redundancy check (CRC) algorithm for integrity check during firmware update makes Ubiquiti airFiber AF2X Radio firmware version 3.2.2 and earlier vulnerable to firmware modification attacks. An attacker can conduct a man-in-the-middle (MITM) attack to modify the new firmware im...
CVE-2023-23120PUBLISHED: 2023-02-02
The use of the cyclic redundancy check (CRC) algorithm for integrity check during firmware update makes TRENDnet TV-IP651WI Network Camera firmware version v1.07.01 and earlier vulnerable to firmware modification attacks. An attacker can conduct a man-in-the-middle (MITM) attack to modify the new fi...
CVE-2023-0651PUBLISHED: 2023-02-02
A vulnerability was found in FastCMS 0.1.0. It has been classified as critical. Affected is an unknown function of the component Template Management. The manipulation leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be u...
CVE-2023-23110PUBLISHED: 2023-02-02
An exploitable firmware modification vulnerability was discovered in certain Netgear products. The data integrity of the uploaded firmware image is ensured with a fixed checksum number. Therefore, an attacker can conduct a MITM attack to modify the user-uploaded firmware image and bypass the checksu...
CVE-2023-0650PUBLISHED: 2023-02-02
A vulnerability was found in YAFNET up to 3.1.11 and classified as problematic. This issue affects some unknown processing of the component Signature Handler. The manipulation leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be...
User Rank: Apprentice
9/23/2015 | 9:35:16 AM
That said....
Q1 - I'm curious though if there are any initiatives in the works to work with these IoT companies when it comes to interacting with security researchers (outside said company/ies), their response and reaction to bugs, exploits, zero days etc that are brought to their attention especially in good faith.
And
Q2 - Once informed, how to categorize and address the disclosed issue within the company. Is it a "stop everything and get this fixed asap" issue because said company may have early beta equipment in-use in the wild (customers) and may feel the issue is enough of a threat to apply most of their resources to fixing said issue (at least those resources necessary to address the issue) even if it means taking those resources away from their current work (perhaps in the midst of meeting a deadline?) I realize it's all contextual and we could all come up with 100 different scenarios but it should be noted that a lot of start-ups are going to be riding a fine line with deadlines, money, perception etc and likely won't be able to weather a misstep quite as well as the larger more established companies.