Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 681758 - (CVE-2011-1142) CVE-2011-1142 Wireshark: Stack consumption vulnerability in BER dissector can cause DoS
CVE-2011-1142 Wireshark: Stack consumption vulnerability in BER dissector can...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20110301,reported=2...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-03-03 02:09 EST by Huzaifa S. Sidhpurwala
Modified: 2015-08-19 05:07 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-08 23:20:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Huzaifa S. Sidhpurwala 2011-03-03 02:09:03 EST
Common Vulnerabilities and Exposures assigned an identifier CVE-2011-1142
the following vulnerability:

Name: CVE-2011-1142
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1142
Assigned: 20110302
Reference: CONFIRM:http://www.wireshark.org/docs/relnotes/wireshark-1.2.15.html
Reference: CONFIRM:http://www.wireshark.org/docs/relnotes/wireshark-1.4.4.html
Reference: CONFIRM:https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516

Stack consumption vulnerability in the dissect_ber_choice function in
the BER dissector in Wireshark 1.2.x through 1.2.15 and 1.4.x through
1.4.4 might allow remote attackers to cause a denial of service
(infinite loop) via vectors involving self-referential ASN.1 CHOICE
values.
Comment 7 Vincent Danen 2015-07-08 23:20:52 EDT
Statement:

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Note You need to log in before you can comment on or make changes to this bug.