public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: glsamaker@gentoo.org
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202312-11 ] SABnzbd: Remote Code Execution
Date: Sat, 23 Dec 2023 08:21:51 -0000	[thread overview]
Message-ID: <170331971122.7.3595545360852111075@da6e833bac34> (raw)

[-- Attachment #1: Type: text/plain, Size: 2645 bytes --]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202312-11
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: High
    Title: SABnzbd: Remote Code Execution
     Date: December 23, 2023
     Bugs: #908032
       ID: 202312-11

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
========

A vulnerability has been found in SABnzbd which allows for remote code
execution.

Background
==========

Free and easy binary newsreader with web interface.

Affected packages
=================

Package           Vulnerable    Unaffected
----------------  ------------  ------------
net-nntp/sabnzbd  < 4.0.2       >= 4.0.2

Description
===========

A vulnerability has been discovered in SABnzbd. Please review the CVE
identifier referenced below for details.

Impact
======

A design flaw was discovered in SABnzbd that could allow remote code
execution. Manipulating the Parameters setting in the Notification
Script functionality allows code execution with the privileges of the
SABnzbd process. Exploiting the vulnerabilities requires access to the
web interface. Remote exploitation is possible if users exposed their
setup to the internet or other untrusted networks without setting a
username/password. By default SABnzbd is only accessible from
`localhost`, with no authentication required for the web interface.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All SABnzbd users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=net-nntp/sabnzbd-4.0.2"

References
==========

[ 1 ] CVE-2023-34237
      https://nvd.nist.gov/vuln/detail/CVE-2023-34237

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202312-11

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 2023 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: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2023-12-23  8:23 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=170331971122.7.3595545360852111075@da6e833bac34 \
    --to=glsamaker@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