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
5/29/2015 | 8:49:57 AM
over the yars PGP has been depreciated by its detractors as "too complex"
Complex systems such as PGP can be made usable by everyone -- just like a "smart phone" -- by means of packaged technology: wrapping the technology in an easy to use human interface -- often called a "GUI" -- or GUI Dialog
Roots
On paper we sign our name with pen&ink. and that signature is characterized by the individual signer,-- pretty hard to duplicate except by a highly skilled forger. even so, with Notaries or witnesses -- the pen& ink signature has been reliable for years.
but in our online digital networks -- whe have -- nothing
except that PGP has been available since the '90s -- and not adopted for general use due to opposition from interests opposed to privacy and security and such
we may now have reached a tipping point where we will have to admit our error and mend our ways
the key factor needed to implement PGP authentications is explanded authentications. Your PGP Public Key needs to be authenticated by a reliable party in order for your signatures to be recognized as valid. Keep these words in mind: In order for your signature to be recognized as valid. This also requires an assurance that YOU made the signature -- not a some scamster. This is possible with PGP because PGP provides both a Public and Private key for each user. The private key is required to make a signature while the public key is required to recognize(authenticate) a signature.
Exactly what we need!
The only issue is in getting the Public Keys authenticated. This should become a service offered by local Credit Unions and Banks. After you generate your key you take it to the Credit Union. They check your ID and then counter-sign it and upload it to the keyserver.
Now you will be able to authenticate your 1040, online banking, shopping &c
SSL/TLS is not acceptable: it is a half-baked system: The server is able to identify itself -- but not the client. Even the server's ID is questionable as the client has only marginal trust for x.509 certificates: he or she has NOT verified and countersigned the x.509 certificates he/she needs to use. This is what enables MITM attacks.