Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-38129PUBLISHED: 2022-08-10A path traversal vulnerability exists in the com.keysight.tentacle.licensing.LicenseManager.addLicenseFile() method in the Keysight Sensor Management Server (SMS). This allows an unauthenticated remote attacker to upload arbitrary files to the SMS host.
CVE-2022-38130PUBLISHED: 2022-08-10
The com.keysight.tentacle.config.ResourceManager.smsRestoreDatabaseZip() method is used to restore the HSQLDB database used in SMS. It takes the path of the zipped database file as the single parameter. An unauthenticated, remote attacker can specify an UNC path for the database file (i.e., \\<at...
CVE-2022-37024PUBLISHED: 2022-08-10Zoho ManageEngine OpManager, OpManager Plus, OpManager MSP, Network Configuration Manager, NetFlow Analyzer, and OpUtils before 2022-07-29 through 2022-07-30 ( 125658, 126003, 126105, and 126120) allow authenticated users to make database changes that lead to remote code execution.
CVE-2022-37003PUBLISHED: 2022-08-10The AOD module has a vulnerability in permission assignment. Successful exploitation of this vulnerability may cause permission escalation and unauthorized access to files.
CVE-2022-37004PUBLISHED: 2022-08-10The Settings application has a vulnerability of bypassing the out-of-box experience (OOBE). Successful exploitation of this vulnerability may affect the availability.
User Rank: Apprentice
8/6/2014 | 11:58:58 AM
That means they are complementary, like the yin and the yang, the masculine and the feminine.
In the same way, you would protect your systems on your network each themselves, but you also make sure no one can reach them if you don't need them to be able to be reached. Those things are also orthogonal.
In IPv6, the idea seems to be that we don't need network encapsulation anymore (NAT) because some moron says "most attacks are coming from application vulnerabilities anyway". But protecting your systems (internally) is orthogonal to not letting outside attackers in without invitations (a firewall) - you can do both at the same time, independent of one another (that's what orthogonal means).
So these are two different directions or dimensions and you can travel both whenever you like, both at the same time, only one and not the other, etcetera.
You can bolster your credentials-that-are-bound-to-one-user based model and at the same time bolster your "you are in unknown territory friend, and I have the upper hand here" model.
It is utterly foolish to suggest that a system needs to be secury only by way of its essential technical design.
A thief that knows a map of your palace will be a much harder threat than someone accidentally stumbling in.
Any thief knows this, so why don't the guards??
Technical open source systems are by definition vulnerable to mass exploits.
Obfuscated systems are, by definition, not.
At the same time, obfuscated systems are vulnerable to single-point attacks. Open source systems are not more vulnerable to those kinds of attacks, than to mass attacks.
Therefore you use both kinds of defense at the same time, and you use both of them to your maximum extent or capability.