CVE-2008-3717: Medium severity harmonyos vulnerability
Published Aug 19, 2008
·Updated
Harmoni before 1.6.0 does not require administrative privileges to list (1) user names or (2) asset ids, which allows remote attackers to obtain sensitive information.
Affected Software
45 affected components
Harmoni Harmoni=0.7.2
Harmoni Harmoni=0.2.0
Harmoni Harmoni=1.0.2
Harmoni Harmoni=1.3.0
Harmoni Harmoni=0.3.2
Harmoni Harmoni=1.0.3
Harmoni Harmoni=0.7.0
Harmoni Harmoni=1.1.0
Harmoni Harmoni=1.3.4
Harmoni Harmoni=0.7.6
Harmoni Harmoni=0.13.4
Harmoni Harmoni=1.4.6
Harmoni Harmoni=0.13.5
Harmoni Harmoni=0.11.0
Harmoni Harmoni=1.3.2
Harmoni Harmoni=0.13.7
Harmoni Harmoni=0.0.5
Harmoni Harmoni=0.0.2
Harmoni Harmoni=0.5.1
Harmoni Harmoni=0.10.1
Harmoni Harmoni=0.12.1
Harmoni Harmoni=0.6.2
Harmoni Harmoni=0.12.3
Harmoni Harmoni=1.0.1
Harmoni Harmoni<=1.4.7
Harmoni Harmoni=0.9.0
Harmoni Harmoni=0.13.2
Harmoni Harmoni=0.13.6
Harmoni Harmoni=0.13.1
Harmoni Harmoni=0.3.0
Harmoni Harmoni=0.7.7
Harmoni Harmoni=1.0.0
Harmoni Harmoni=0.1.0
Harmoni Harmoni=0.6.0
Harmoni Harmoni=0.13.0
Harmoni Harmoni=0.12.0
Harmoni Harmoni=0.0.4
Harmoni Harmoni=0.0.3
Harmoni Harmoni=0.3.1
Harmoni Harmoni=1.3.5
Harmoni Harmoni=1.4.2
Harmoni Harmoni=1.0.5
Harmoni Harmoni=0.7.1
Harmoni Harmoni=1.0.6
Harmoni Harmoni=0.13.3
Event History
Aug 19, 2008
CVE Published
via MITRE·07:10 PM
Data Sourced
via MITRE·07:10 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2008-3717?
CVE-2008-3717 is considered a medium severity vulnerability due to its potential to expose sensitive information.
2
How do I fix CVE-2008-3717?
To fix CVE-2008-3717, upgrade Harmoni to version 1.6.0 or later which addresses this vulnerability.
3
What types of information can be exposed by CVE-2008-3717?
CVE-2008-3717 allows remote attackers to list user names and asset IDs, leading to potential information disclosure.
4
Which versions of Harmoni are affected by CVE-2008-3717?
Harmoni versions prior to 1.6.0 are affected by CVE-2008-3717.
5
Is there a workaround for CVE-2008-3717?
There are no documented workarounds for CVE-2008-3717; upgrading to the fixed version is recommended.