Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-1142PUBLISHED: 2023-03-27In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use URL decoding to retrieve system files, credentials, and bypass authentication resulting in privilege escalation.
CVE-2023-1143PUBLISHED: 2023-03-27In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use Lua scripts, which could allow an attacker to remotely execute arbitrary code.
CVE-2023-1144PUBLISHED: 2023-03-27Delta Electronics InfraSuite Device Master versions prior to 1.0.5 contains an improper access control vulnerability in which an attacker can use the Device-Gateway service and bypass authorization, which could result in privilege escalation.
CVE-2023-1145PUBLISHED: 2023-03-27Delta Electronics InfraSuite Device Master versions prior to 1.0.5 are affected by a deserialization vulnerability targeting the Device-DataCollect service, which could allow deserialization of requests prior to authentication, resulting in remote code execution.
CVE-2023-1655PUBLISHED: 2023-03-27Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.4.0.
User Rank: Ninja
10/26/2016 | 9:14:33 AM
Email doesn't work that way...and from time to time you're going to get unfamiliar senders (and, therefore, non-whitelisted senders) who are sending legitimate email.
Of course, all of these emails could be "authenticated," but then what if someone who has authentication via a certificate authority then decides to become a bad actor?
The easy rebuttal to this is that, "Well, that's okay, because we'll have their identity -- and can thereby revoke their authentication."
But then that gets us down the data-privacy rabbit hole.
It's one thing for online retailers and other sellers / companies to authenticate themselves publicly. It's another thing to ask people to authenticate themselves for private communication.
Or what am I missing here?