Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 552694 - <sys-libs/glibc-2.21: ADDW macro vulnerabilities (CVE-2015-{1472,1473})
Summary: <sys-libs/glibc-2.21: ADDW macro vulnerabilities (CVE-2015-{1472,1473})
Status: RESOLVED DUPLICATE of bug 538814
Alias: None
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: Gentoo Security
URL:
Whiteboard: A2 [ebuild]
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-21 00:25 UTC by GLSAMaker/CVETool Bot
Modified: 2015-07-21 03:16 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description GLSAMaker/CVETool Bot gentoo-dev 2015-06-21 00:25:24 UTC
CVE-2015-1473 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-1473):
  The ADDW macro in stdio-common/vfscanf.c in the GNU C Library (aka glibc or
  libc6) before 2.21 does not properly consider data-type size during a
  risk-management decision for use of the alloca function, which might allow
  context-dependent attackers to cause a denial of service (segmentation
  violation) or overwrite memory locations beyond the stack boundary via a
  long line containing wide characters that are improperly handled in a wscanf
  call.

CVE-2015-1472 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-1472):
  The ADDW macro in stdio-common/vfscanf.c in the GNU C Library (aka glibc or
  libc6) before 2.21 does not properly consider data-type size during memory
  allocation, which allows context-dependent attackers to cause a denial of
  service (buffer overflow) or possibly have unspecified other impact via a
  long line containing wide characters that are improperly handled in a wscanf
  call.
Comment 1 Agostino Sarubbo gentoo-dev 2015-06-22 07:57:45 UTC
looks like a duplicate of 538814
Comment 2 SpanKY gentoo-dev 2015-07-21 03:15:34 UTC
(In reply to Agostino Sarubbo from comment #1)

upstream treated it that way -- one bug & one fix

*** This bug has been marked as a duplicate of bug 538814 ***