-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                              ESB-2021.1135.2
                   Grafana vulnerability CVE-2019-15043
                                1 July 2021

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           BIG-IQ Centralized Management
Publisher:         F5 Networks
Operating System:  Network Appliance
Impact/Access:     Denial of Service -- Remote/Unauthenticated
Resolution:        Patch/Upgrade
CVE Names:         CVE-2019-15043  

Original Bulletin: 
   https://support.f5.com/csp/article/K00843201

Revision History:  July  1 2021: Vendor updated advisory to include fix information
                   April 6 2021: Initial Release

- --------------------------BEGIN INCLUDED TEXT--------------------

K00843201: Grafana vulnerability CVE-2019-15043

Original Publication Date: 03 Apr, 2021
Latest   Publication Date: 01 Jul, 2021

Security Advisory Description

In Grafana 2.x through 6.x before 6.3.4, parts of the HTTP API allow
unauthenticated use. This makes it possible to run a denial of service attack
against the server running Grafana. (CVE-2019-15043)

Impact

An unauthorized user may be able to leverage the Grafana component to run a
snapshot task on the system.

Security Advisory Status

F5 Product Development has assigned ID 1008397 (BIG-IQ) to this vulnerability.

To determine if your product and version have been evaluated for this
vulnerability, refer to the Applies to (see versions) box. To determine if your
release is known to be vulnerable, the components or features that are affected
by the vulnerability, and for information about releases, point releases, or
hotfixes that address the vulnerability, refer to the following table. For more
information about security advisory versioning, refer to K51812227:
Understanding security advisory versioning.

Note: After a fix is introduced for a vulnerable version, that fix applies to
all subsequent point releases for that version and no additional fixes for that
version will be listed in the table. For example, when a fix is introduced in
14.1.2.3, the fix applies to 14.1.2.4 and all later point releases.

+------------+------+--------------+----------+----------+------+-------------+
|            |      |Versions known|Fixes     |          |CVSSv3|Vulnerable   |
|Product     |Branch|to be         |introduced|Severity  |score^|component or |
|            |      |vulnerable^1  |in        |          |2     |feature      |
+------------+------+--------------+----------+----------+------+-------------+
|            |16.x  |None          |Not       |          |      |             |
|            |      |              |applicable|          |      |             |
|            +------+--------------+----------+          |      |             |
|            |15.x  |None          |Not       |          |      |             |
|            |      |              |applicable|          |      |             |
|            +------+--------------+----------+          |      |             |
|            |14.x  |None          |Not       |          |      |             |
|BIG-IP (all |      |              |applicable|Not       |      |             |
|modules)    +------+--------------+----------+vulnerable|None  |None         |
|            |13.x  |None          |Not       |          |      |             |
|            |      |              |applicable|          |      |             |
|            +------+--------------+----------+          |      |             |
|            |12.x  |None          |Not       |          |      |             |
|            |      |              |applicable|          |      |             |
|            +------+--------------+----------+          |      |             |
|            |11.x  |None          |Not       |          |      |             |
|            |      |              |applicable|          |      |             |
+------------+------+--------------+----------+----------+------+-------------+
|            |8.x   |8.0.0         |8.1.0     |          |      |             |
|BIG-IQ      +------+--------------+----------+          |      |             |
|Centralized |7.x   |7.0.0 - 7.1.0 |None      |High      |7.5   |Grafana      |
|Management  +------+--------------+----------+          |      |             |
|            |6.x   |6.0.0 - 6.1.0 |None      |          |      |             |
+------------+------+--------------+----------+----------+------+-------------+
|F5OS        |1.x   |None          |Not       |Not       |None  |None         |
|            |      |              |applicable|vulnerable|      |             |
+------------+------+--------------+----------+----------+------+-------------+
|Traffix SDC |5.x   |None          |Not       |Not       |None  |None         |
|            |      |              |applicable|vulnerable|      |             |
+------------+------+--------------+----------+----------+------+-------------+

^1F5 only evaluates software versions that have not yet reached the End of
Technical Support (EoTS) phase of their lifecycle.

^2The CVSSv3 score link takes you to a resource outside of AskF5, and it is
possible that the document may be removed without our knowledge.

Recommended Actions

If you are running a version listed in the Versions known to be vulnerable
column, you can eliminate this vulnerability by installing a version listed in
the Fixes introduced in column. If the Fixes introduced in column does not list
a version for your branch, then no update candidate currently exists for that
branch and F5 recommends upgrading to a version with the fix (refer to the
table).

If the Fixes introduced in column lists a version prior to the one you are
running, in the same branch, then your version should have the fix.

Mitigation

To mitigate this vulnerability, you can modify the webd configuration file to
deny access to the snapshot API endpoint. To do so, perform the following
procedure.

Impact of action: This procedure involves restarting the webd daemon, which
causes the BIG-IQ user interface to be inaccessible. F5 recommends performing
this procedure during a scheduled maintenance window.

Modify the 'webd' configuration file to deny access to the snapshot API
endpoint

Create a backup of the 'webd' configuration file

 1. Log in to the BIG-IQ system Advanced Shell (bash) using administrator role
    credentials.
 2. Create a backup copy of the webd configuration file by typing the following
    command:

    cp -a /etc/webd/webd.conf /etc/webd/webd.conf.backup

Modify the 'webd' configuration file

Use the text editor of your choice to modify the /etc/webd/webd.conf file.

 1. Locate the following stanza in the configuration file:

      location /mgmt/grafana/api/datasources/proxy/ {
        deny all;
        return 404;
      }

 2. Insert the following stanza directly after the /mgmt/grafana/api/
    datasources/proxy/ stanza:

      location /mgmt/grafana/api/snapshots {
        deny all;
        return 404;
      }

 3. Confirm that the entire section appears similar to the following example:

      location /mgmt/grafana/ {
        proxy_pass              http://grafana/;
        proxy_set_header        Host             $hostname:$proxy_port;
        proxy_set_header        X-Real-IP         $remote_addr;
        proxy_set_header        X-Forwarded-For  $proxy_add_x_forwarded_for;
        proxy_connect_timeout   5s;
        proxy_read_timeout      300s;
        # completely disallow all access through the grafana data source proxy
        # TODO: Move this to the /mgmt/ block after the auth proxy is in place
        location /mgmt/grafana/api/datasources/proxy/ {
          deny all;
          return 404;
        }
        location /mgmt/grafana/api/snapshots {
          deny all;
          return 404;
        }
      }

 4. Save the changes and exit the text editor.

Verify the file and restart the daemon

 1. Verify that the configuration file is valid, by typing the following
    command:

    webd -t

    The output should appear similar to the following example:

    webd: the configuration file /etc/webd/webd.conf syntax is ok
    webd: configuration file /etc/webd/webd.conf test is successful

 2. Restart the webd daemon by typing the following command:

    tmsh restart sys service webd

Supplemental Information

o K14736: BIG-IQ daemons
  o K41942608: Overview of security advisory articles
  o K4602: Overview of the F5 security vulnerability response policy
  o K4918: Overview of the F5 critical issue hotfix policy
  o K8986: F5 software lifecycle policy
  o K9970: Subscribing to email notifications regarding F5 products
  o K9957: Creating a custom RSS feed to view new and updated documents

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

        https://www.auscert.org.au/bulletins/

===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967

iQIVAwUBYN0mqeNLKJtyKPYoAQjtTQ//XqEn3HtqDGZf6yf8W98jkbktTAW+a9mK
aU5GrIp5OhO9VAkzor+cT9X0jgJR1xC20IUxkc5zYh+MowLGuObT1scMau2Pzrh/
ZpUSBRjHc0enEb8H1DZLdDEbNiPMvio5H1aPaDHMSqw03bfE78crFiqPnD+FD9gh
fS/hKeOEUaZELjwcG4HyjNvuh16xI3PuEu26O1wby812yvaLZON+lE31kRstjDf2
jaHYpt7+2nQdbg1YoHJzcoswE8kMAFpoYvcflBjmTYtSTPHG2nYOSOdCH8KL9CHr
teUgIqwzsGbzaoS5JZ+DInwqRSLKnU0Lu0HvTTmtAd5H3LiJVCP1g31jpLBqqFWy
qjqz/3k0mbJ1kyQ+oV5Fc3TpVf3jNCn2k5tPnlDWaFOwTc+XB/2SEIB7DH5NfK1K
DJMP1ybFwwffKHykjBPooKnMHVclpRXFPN3pTIEOaAyheGHPOBxc3gZJ5GUs0be9
jlq/eZAo4h4h47+xrtlSSXAjMbjISDKAFqtPCPF37R+O9oSyNYKwZKroKGwmkfP5
fnqt3Q0LR0zqIYVEVULawNQQ+P1CgXAN9FNIE4X3djEpKW0KtIcIcZ9DP4/+aLQd
YDXeJsf7Ekhwu8U9XwiDNrr6qlgrRW+uotY3mt3K2QD0DUDfTg29r2jco+W1YPtQ
epEiSQdcQCA=
=Fmxp
-----END PGP SIGNATURE-----