Bug 36953 - augeas: Multiple issues (4.1)
augeas: Multiple issues (4.1)
Status: CLOSED WONTFIX
Product: UCS
Classification: Unclassified
Component: Security updates
UCS 4.1
Other Linux
: P5 minor (vote)
: ---
Assigned To: UCS maintainers
:
Depends on: 45356
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-24 10:14 CET by Moritz Muehlenhoff
Modified: 2019-04-11 19:23 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Security Issue
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score: 7.8 (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Muehlenhoff univentionstaff 2014-11-24 10:14:31 CET
Multiple symlink races in aureas (CVE-2012-0786, CVE-2012-0787, CVE-2012-6607)
Comment 1 Arvid Requate univentionstaff 2015-05-06 23:23:12 CEST
The three issues above have been classified as "Minor issue" in Debian.
Comment 2 Stefan Gohmann univentionstaff 2015-09-01 14:18:25 CEST
Only minor issue(s). Removing target milestone.
Comment 3 Arvid Requate univentionstaff 2017-09-08 13:34:07 CEST
Upstream Debian package version 0.10.0-1+deb7u1 fixes:

* Augeas versions up to and including 1.8.0 are vulnerable to heap-based buffer overflow due to improper handling of escaped strings. Attacker could send crafted strings that would cause the application using augeas to copy past the end of a buffer, leading to a crash or possible code execution. (CVE-2017-7555)
Comment 4 Arvid Requate univentionstaff 2018-04-17 15:56:21 CEST
This issue has been filed against UCS 4.1.

UCS 4.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.