Bug 508061 - (CVE-2009-1886) CVE-2009-1886 samba format string vulnerabilities
CVE-2009-1886 samba format string vulnerabilities
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
http://web.nvd.nist.gov/view/vuln/det...
impact=none,source=upstream,reported=...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-25 08:42 EDT by Vincent Danen
Modified: 2009-07-03 17:07 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-06-25 08:51:49 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 Vincent Danen 2009-06-25 08:42:12 EDT
Common Vulnerabilities and Exposures assigned an identifier CVE-2009-1886 to
the following vulnerability:

Name: CVE-2009-1886
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1886
Assigned: 20090602
Reference: CONFIRM: http://www.samba.org/samba/ftp/patches/security/samba-3.2.12-CVE-2009-1886.patch
Reference: CONFIRM: http://www.samba.org/samba/security/CVE-2009-1886.html
Reference: CONFIRM: https://bugzilla.samba.org/show_bug.cgi?id=6478
Reference: BID:35472
Reference: URL: http://www.securityfocus.com/bid/35472
Reference: SECUNIA:35539
Reference: URL: http://secunia.com/advisories/35539
Reference: VUPEN:ADV-2009-1664
Reference: URL: http://www.vupen.com/english/advisories/2009/1664

Multiple format string vulnerabilities in client/client.c in smbclient
in Samba 3.2.0 through 3.2.12 might allow context-dependent attackers
to execute arbitrary code via format string specifiers in a filename.
Comment 1 Vincent Danen 2009-06-25 08:51:49 EDT
Red Hat Enterprise Linux 5 and earlier provide Samba 3.0.x which is not vulnerable to this issue.

This issue is also caught by fortify source on Fedora and as a result is a non-issue.

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