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 WNR612v2 Wireless Routers firmware version 1.0.0.3 and earlier. 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...
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: Ninja
10/30/2016 | 12:41:23 PM
Considering they telephoned me, and considering that the number they were calling from was not a telephone number known to me to be associated w/ my carrier, I refused. The huffy person on the other end of the line appeared put out.
I then called my insurance company on the number I knew to be correct to ask them about it. Unfortunately, it's such a big bureaucracy that I couldn't even get through to someone who could even tell me whether or not the call was legitimate for sure.
Because my insurance company was so bureaucratic and stupid, I wouldn't put it past them to have such stupid practices -- but it's also just as likely (at least) that it was a malfeasor's bit of social engineering. In any case, nothing bad happened to me because I refused to "verify" my information.
People calling you asking you to "verify" your information is the slightly more sophisticated social-engineering equivalent of someone calling you and after you say hello, the other person on the line immediately says, "Who's this?" YOU CALLED ME. >:P