GeoVision Digital Video Surveillance weak authentication
| geovision-authentication (20537) |  Medium Risk |
Description:
GeoVision Digital Video Surveillance System could allow a remote attacker to view the JPEG images caused by the lack of authentication when attempting to view the JPEG images. A remote attacker could exploit this vulnerability to view the JPEG images.
Consequences:
Obtain Information
Remedy:
Upgrade to the latest version of GeoVision Digital Video Surveillance System (7.0 or later) , available from the GeoVision Digital Video Surveillance System Web site. See References.
References:
- BugTraq Mailing List, Mon May 09 2005 - 20:17:43 CDT : GeoVision Digital Video Surveillance System - Multiple authentication iss.
- Esqo Security Advisory 100505-1: GeoVision Digital Video Surveillance System - Multiple authentication issues.
- GeoVision Digital Video Surveillance Web site: Digital Video Surveillance System.
- BID-13571: GeoVision Digital Surveillance System Unauthorized JPEG Image Access Vulnerability
- CVE-2005-1552: GeoVision Digital Video Surveillance System 6.04, 6.1 and 7.0, when set to create JPEG images, does not properly protect an image even when a password and username is assigned, which may allow remote attackers to gain sensitive information via a direct request to the image.
- SA15330: GeoVision Digital Video Surveillance System Authentication Bypass
Platforms Affected:
- Camera Security Now GeoVision Digital Video Surveillance 6.04
- Camera Security Now GeoVision Digital Video Surveillance 6.1
- Camera Security Now GeoVision Digital Video Surveillance 7.0
Reported:
May 10, 2005
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net