Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2020.4110
The BIG-IP CFE logs sensitive Azure storage account credentials
19 November 2020
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: BIG-IP Products
Publisher: F5 Networks
Operating System: Network Appliance
Impact/Access: Modify Arbitrary Files -- Existing Account
Access Confidential Data -- Existing Account
Reduced Security -- Existing Account
Resolution: Patch/Upgrade
Original Bulletin:
https://support.f5.com/csp/article/K21125762
- --------------------------BEGIN INCLUDED TEXT--------------------
K21125762: The BIG-IP CFE logs sensitive Azure storage account credentials
Original Publication Date: 18 Nov, 2020
Security Advisory Description
The BIG-IP Cloud Failover Extension (CFE) logs sensitive Azure storage account
credentials in /var/log/restnoded/restnoded.log.
This issue occurs when all of the following conditions are met:
o You configure the CFE to provide failover functionality for your BIG-IP
systems in Azure. For more information on CFE, refer to CFE Overview on
CloudDocs.
o You increase the CFE logging level on the BIG-IP system to Silly. The
default value is Info. For more information, refer to Logging in CloudDocs.
Impact
A malicious user who has access to the BIG-IP system log files can use the
leaked storage account name and access key to access your Azure storage to
read, write, or delete files.
Symptoms
As a result of this issue, you may encounter the following symptom:
o You observe your Azure account name and access key logged in the /var/log/
restnoded/restnoded.log file on the BIG-IP system.
Security Advisory Status
F5 Product Development has assigned ID 964813 to this issue. F5 has confirmed
that this issue exists in the products listed in the Applies to (see versions)
box, located in the upper-right corner of this article. For information about
releases, point releases, or hotfixes that resolve this issue, refer to the
following table.
+------------------------+-------------------+-----------------------+
|Type of fix |Fixes introduced in|Related articles |
+------------------------+-------------------+-----------------------+
|Release |None |None |
+------------------------+-------------------+-----------------------+
|Point release/hotfix |None |None |
+------------------------+-------------------+-----------------------+
|Cloud Failover Extension|1.6.1 |Cloud Failover Releases|
+------------------------+-------------------+-----------------------+
Security Advisory Recommended Actions
Workaround
To eliminate this issue, you can upgrade to a version listed in the Fixes
introduced in column and delete the log files containing the Azure credentials.
Additionally, if you suspect that the Storage Account name and keys have been
exposed to untrusted users, you should regenerate the Azure Storage Account
access key and reset the CFE on the BIG-IP system.
Impact of workaround: Performing the following procedures updates and resets
the CFE. F5 recommends that you perform these procedures during a scheduled
maintenance window.
o Upgrade the CFE
o Delete the log files containing the Azure credentials.
o Regenerate the Azure Storage Account access key.^1
o Reset the CFE on the BIG-IP system^1
^1Perform this procedure when you suspect that the Storage Account name and
keys have been exposed to untrusted users.
Upgrade the CFE
To upgrade the CFE, download the CFE package from GitHub and upload and install
the package on the BIG-IP systems. For more information, refer to Download and
Install Cloud Failover Extension.
Delete the log files containing the Azure credentials
Delete the log files /var/log/restnoded/restnoded* containing the Azure account
credentials on the affected BIG-IP system.
Regenerate the Azure Storage Account access key
To regenerate your access key, refer to Manage storage account access keys and
Storage Accounts - Regenerate Key.
Note: These links take you to a resource outside of AskF5, and it is possible
that the document may be removed without our knowledge.
Reset the CFE on the BIG-IP system
To reset the CFE on your BIG-IP systems, you can send a "resetStateFile": true
json content to the /reset REST endpoint. You can use a command such as curl,
as shown in the following example:
curl --header "Content-Type: application/json" --request POST --data '
{"resetStateFile": true}' -ku example_user:example_password https://:
<IP_address>/mgmt/shared/cloud-failover/reset
For more information on the /reset endpoint, refer to the API Reference
Documentation.
Supplemental Information
o K51812227: Understanding security advisory versioning
o K41942608: Overview of AskF5 security advisory articles
o K4602: Overview of the F5 security vulnerability response policy
o K4918: Overview of the F5 critical issue hotfix policy
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
o K167: Downloading software and firmware from F5
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
iQIVAwUBX7XbgeNLKJtyKPYoAQikEQ//QW8ux7/UFGHyY1xjE92cVVhWfGus7e7d
BoL7n3nz5qlumLDy9ArOx0pfP63o6kFyc9/iedFZ8e/xmFCPaJ7Zb5SGcrXtTeI2
iWinl+JEvtubMIx9R4IAFhvWX/gYnhoDLdbPCgnkwYHTO74VyWj9avWhtIIHOdNv
31sJskxqYw5Ax6NLdWu7hpvvaTyxurkqKMX38XVIP57oKpGzxXQPaCd8NGo1Tltg
VSx0yAHyNqUn+zKpP15Yn13Q2guQ0HWA3ssvXILyreCS5bfMYvzb/xaIUbAWpuQa
vJ7yRPnslQK/y51NZAiEOyPrjrIUJ1tmFxZp43f6UkDwBBGXIdROxGoCMWMdOlqA
D3Sbl+NL4/eUWISO0NBMKtMel661zMI5x7LtWPX5VohwZlft1B1v3nP6nA2ZK8k0
HR7RVYgt8C3S4uu6ylSNldlV7G9EXOIIfPEhQvlIWFcF/XWFgMJ+bkUBxOLNPQkI
q2GLpqU/H9RtBa5d6nSGXQ3VtxIBSvqOMt2EpgrPC8ceCzDI4qMOkPCcE4vofASb
TG3FXJQ5VCyCaKq1cgWvlV7eTTc1/6PrjGD8VC9bKd0tr6tzr9UhQzhv0nUmEPtd
kaRp2jsquqV2eh3/simLMTxwzHfMsSW1A5uGIzGqe7cpm21HcOE8bRfVDgZjxdgo
k9BaOcHOA0w=
=Emn3
-----END PGP SIGNATURE-----