CVE-2017-7683: Infoleak
Published Jul 14, 2017
·Updated
Apache OpenMeetings 1.0.0 displays Tomcat version and detailed error stack trace, which is not secure.
Affected Software
21 affected components
Apache OpenMeetings=1.0.0
Apache OpenMeetings=2.0
Apache OpenMeetings=2.1
Apache OpenMeetings=2.1.1
Apache OpenMeetings=2.2.0
Apache OpenMeetings=3.0.0
Apache OpenMeetings=3.0.1
Apache OpenMeetings=3.0.2
Apache OpenMeetings=3.0.3
Apache OpenMeetings=3.0.4
Apache OpenMeetings=3.0.5
Apache OpenMeetings=3.0.6
Apache OpenMeetings=3.0.7
Apache OpenMeetings=3.1.0
Apache OpenMeetings=3.1.1
Apache OpenMeetings=3.1.2
Apache OpenMeetings=3.1.3
Apache OpenMeetings=3.1.4
Apache OpenMeetings=3.1.5
Apache OpenMeetings=3.2.0
Apache OpenMeetings=3.2.1
Event History
Jul 14, 2017
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2017-7683?
CVE-2017-7683 is classified as a medium severity vulnerability due to its potential exposure of sensitive information.
2
How do I fix CVE-2017-7683?
To fix CVE-2017-7683, upgrade Apache OpenMeetings to a version that does not display Tomcat information and detailed error stack traces.
3
Which versions of Apache OpenMeetings are affected by CVE-2017-7683?
CVE-2017-7683 affects Apache OpenMeetings versions 1.0.0 and 2.0 through 3.2.1.
4
What kind of information does CVE-2017-7683 expose?
CVE-2017-7683 exposes the Tomcat version and detailed error stack traces, which could help attackers exploit the application.
5
Is CVE-2017-7683 a network vulnerability?
CVE-2017-7683 is not specifically a network vulnerability but rather an application security issue that can lead to information disclosure.