Published : 2018-07-03 19:29 Updated : 2019-10-09 23:26
CVSS Score More info
Score 3.5 / 10
A vulnerability exploitable with network access means the vulnerable software is bound to the network stack and the attacker does not require local network access or local access. Such a vulnerability is often termed "remotely exploitable". An example of a network attack is an RPC buffer overflow.
The access conditions are somewhat specialized; the following are examples:
- The attacking party is limited to a group of systems or users at some level of authorization, possibly untrusted.
- Some information must be gathered before a successful attack can be launched.
- The affected configuration is non-default, and is not commonly configured (e.g., a vulnerability present when a server performs user account authentication via a specific scheme, but not present for another authentication scheme).
- The attack requires a small amount of social engineering that might occasionally fool cautious users (e.g., phishing attacks that modify a web browsers status bar to show a false link, having to be on someones buddy list before sending an IM exploit).
The vulnerability requires an attacker to be logged into the system (such as at a command line or via a desktop session or web interface).
There is no impact to the confidentiality of the system.
Modification of some system files or information is possible, but the attacker does not have control over what can be modified, or the scope of what the attacker can affect is limited. For example, system or application files may be overwritten or modified, but either the attacker has no control over which files are affected or the attacker can modify files within only a limited context or scope.
There is no impact to the availability of the system.
|Ibm||Rational Collaborative Lifecycle Management||5.0||cpe:/a:ibm:rational_collaborative_lifecycle_management:5.0|
|Ibm||Rational Collaborative Lifecycle Management||5.0.1||cpe:/a:ibm:rational_collaborative_lifecycle_management:5.0.1|
|Ibm||Rational Collaborative Lifecycle Management||5.0.2||cpe:/a:ibm:rational_collaborative_lifecycle_management:5.0.2|
|Ibm||Rational Collaborative Lifecycle Management||6.0||cpe:/a:ibm:rational_collaborative_lifecycle_management:6.0|
|Ibm||Rational Collaborative Lifecycle Management||6.0.1||cpe:/a:ibm:rational_collaborative_lifecycle_management:6.0.1|
|Ibm||Rational Collaborative Lifecycle Management||6.0.2||cpe:/a:ibm:rational_collaborative_lifecycle_management:6.0.2|
|Ibm||Rational Collaborative Lifecycle Management||6.0.3||cpe:/a:ibm:rational_collaborative_lifecycle_management:6.0.3|
|Ibm||Rational Collaborative Lifecycle Management||6.0.4||cpe:/a:ibm:rational_collaborative_lifecycle_management:6.0.4|
|Ibm||Rational Collaborative Lifecycle Management||6.0.5||cpe:/a:ibm:rational_collaborative_lifecycle_management:6.0.5|
|Ibm||Rational Quality Manager||5.0||cpe:/a:ibm:rational_quality_manager:5.0|
|Ibm||Rational Quality Manager||5.0.1||cpe:/a:ibm:rational_quality_manager:5.0.1|
|Ibm||Rational Quality Manager||5.0.2||cpe:/a:ibm:rational_quality_manager:5.0.2|
|Ibm||Rational Quality Manager||6.0||cpe:/a:ibm:rational_quality_manager:6.0|
|Ibm||Rational Quality Manager||6.0.1||cpe:/a:ibm:rational_quality_manager:6.0.1|
|Ibm||Rational Quality Manager||6.0.2||cpe:/a:ibm:rational_quality_manager:6.0.2|
|Ibm||Rational Quality Manager||6.0.3||cpe:/a:ibm:rational_quality_manager:6.0.3|
|Ibm||Rational Quality Manager||6.0.4||cpe:/a:ibm:rational_quality_manager:6.0.4|
|Ibm||Rational Quality Manager||6.0.5||cpe:/a:ibm:rational_quality_manager:6.0.5|
History of changes