Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-10072PUBLISHED: 2023-02-04
A vulnerability classified as problematic was found in NREL api-umbrella-web 0.7.1. This vulnerability affects unknown code of the component Flash Message Handler. The manipulation leads to cross site scripting. The attack can be initiated remotely. Upgrading to version 0.8.0 is able to address this...
CVE-2018-25079PUBLISHED: 2023-02-04
A vulnerability was found in Segmentio is-url up to 1.2.2. It has been rated as problematic. Affected by this issue is some unknown functionality of the file index.js. The manipulation leads to inefficient regular expression complexity. The attack may be launched remotely. Upgrading to version 1.2.3...
CVE-2023-0671PUBLISHED: 2023-02-04Code Injection in GitHub repository froxlor/froxlor prior to 2.0.10.
CVE-2023-24806PUBLISHED: 2023-02-04** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This CVE has been rejected as it was incorrectly assigned. All references and descriptions in this candidate have been removed to prevent accidental usage.
CVE-2013-10017PUBLISHED: 2023-02-04
A vulnerability was found in fanzila WebFinance 0.5. It has been classified as critical. Affected is an unknown function of the file htdocs/admin/save_roles.php. The manipulation of the argument id leads to sql injection. The name of the patch is 6cfeb2f6b35c1b3a7320add07cd0493e4f752af3. It is recom...
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.