From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201806-03 ] BURP: Multiple vulnerabilities
Date: Wed, 13 Jun 2018 16:56:21 -0400 [thread overview]
Message-ID: <2281079.TXyzaM4Thh@monkey> (raw)
[-- Attachment #1: Type: text/plain, Size: 2465 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201806-03
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: BURP: Multiple vulnerabilities
Date: June 13, 2018
Bugs: #628770, #641842
ID: 201806-03
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Multiple vulnerabilities were discovered in BURP's Gentoo ebuild, the
worst of which could lead to root privilege escalation.
Background
==========
A network backup and restore program.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 app-backup/burp < 2.1.32 >= 2.1.32
Description
===========
It was discovered that Gentoo's BURP ebuild does not properly set
permissions or place the pid file in a safe directory.
Impact
======
A local attacker could escalate privileges.
Workaround
==========
Users should ensure the proper permissions are set as discussed in the
referenced bugs.
Resolution
==========
All BURP users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-backup/burp-2.1.32"
References
==========
[ 1 ] CVE-2017-18284
https://nvd.nist.gov/vuln/detail/CVE-2017-18284
[ 2 ] CVE-2017-18285
https://nvd.nist.gov/vuln/detail/CVE-2017-18285
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201806-03
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.
License
=======
Copyright 2018 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
https://creativecommons.org/licenses/by-sa/2.5
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2018-06-13 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2281079.TXyzaM4Thh@monkey \
--to=bman@gentoo.org \
--cc=gentoo-announce@lists.gentoo.org \
--cc=security@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox