Published:2012/01/11  Last Updated:2012/01/12

JVN#63249231
Cogent DataHub vulnerable to HTTP header injection

Overview

Cogent DataHub provided by Cogent Real-Time Systems Inc. contains a HTTP header injection vulnerability.

Products Affected

  • Cogent DataHub 7.1.2 and earlier
  • OPC DataHub 6.4.20 and earlier
  • Cascade DataHub V6.4.20 and earlier

Description

Cogent DataHub provided by Cogent Real-Time Systems Inc. contains a HTTP header injection vulnerability (also known as CRLF, carriage return line feed, injection vulnerability). 

Impact

If a remote attacker sends a crafted HTTP header to a vulnerable system,  forged information may be displayed on the user's web browser or an HTTP response splitting attack may be conducted.

Solution

Update the Software
Update the software to the latest version according to the information provided by the developer.

Vendor Status

Vendor Link
Cogent Real-Time Systems Inc. Release Notes
Download Software

References

JPCERT/CC Addendum

Vulnerability Analysis by JPCERT/CC

Analyzed on 2012.01.11

Measures Conditions Severity
Access Required can be attacked over the Internet using packets
  • High
Authentication anonymous or no authentication (IP addresses do not count)
  • High
User Interaction Required the user must be convinced to take a standard action that does not feel harmful to most users, such as click on a link or view a file
  • Mid
Exploit Complexity the user must be convinced to take a difficult or suspicious action. If the honest user must have elevated privileges, they are likely to be more suspiciouse
  • High

Description of each analysis measures

Credit

Kuang-Chun Hung of Security Research and Service Institute - Information and Communication Security Technology Center (ICST), Taiwan R.O.C. reported this vulnerability to JPCERT/CC.
JPCERT/CC coordinated with the developer under Information Security Early Warning Partnership.

Other Information

JPCERT Alert
JPCERT Reports
CERT Advisory
CPNI Advisory
TRnotes
CVE CVE-2012-0310
JVN iPedia JVNDB-2012-000002

Update History

2012/01/12
Information under the section [Products Affected] was updated.