ESB-2018.0096.2 - UPDATE [Appliance] F5 Products: Access privileged data - Existing account 2018-01-22

Printable version
PGP/GPG verifiable version

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

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

                              ESB-2018.0096.2
             K91229003: Side-channel processor vulnerabilities
              CVE-2017-5715, CVE-2017-5753, and CVE-2017-5754
                              22 January 2018

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

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

Product:           F5 Products
Publisher:         F5 Networks
Operating System:  Network Appliance
Impact/Access:     Access Privileged Data -- Existing Account
Resolution:        Patch/Upgrade
CVE Names:         CVE-2017-5754 CVE-2017-5753 CVE-2017-5715

Reference:         ASB-2018.0002.4
                   ESB-2018.0090
                   ESB-2018.0089
                   ESB-2018.0046
                   ESB-2018.0044
                   ESB-2018.0042

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

Revision History:  January 22 2018: Completed table outlining vulnerability of 
                                    F5 products to SPECTRE and METLDOWN based 
                                    on processor type
                   January  9 2018: Initial Release

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

K91229003: Side-channel processor vulnerabilities CVE-2017-5715, CVE-2017-5753,
and CVE-2017-5754

Security Advisory

Original Publication Date: Jan 04, 2018
Updated Date: Jan 20, 2018

Security Advisory Description

There are three separate, related issues included in this advisory. All require
the attacker to induce speculative execution of code to acquire privileged
information, then leak that information via a micro-architectural side-channel.
Certain Intel processors are vulnerable to all three issues; AMD and ARM
processors may be vulnerable to one or two of the issues. The following three
side-channel attacks were publicly disclosed on January 3, 2018:

  o CVE-2017-5753 (also known as Spectre Variant 1) Bounds checking bypass

    Systems with microprocessors utilizing speculative execution and branch
    prediction may allow unauthorized disclosure of information to an attacker
    with local user access via a side-channel analysis.

  o CVE-2017-5715 (also known as Spectre Variant 2) Branch target injection

    Systems with microprocessors utilizing speculative execution and indirect
    branch prediction may allow unauthorized disclosure of information to an
    attacker with local user access via a side-channel analysis.

  o CVE-2017-5754 (also known as Meltdown) Rogue data cache load

    Systems with microprocessors utilizing speculative execution and indirect
    branch prediction may allow unauthorized disclosure of information to an
    attacker with local user access via a side-channel analysis of the data
    cache.

Impact

For products with None in the Versions known to be vulnerable column, there is
no impact.

For products with ** in the various columns, F5 is still researching the issue
and will update this article after confirming the required information. F5
Technical Support has no additional information about this issue.

BIG-IP

All three vulnerabilities require an attacker capable of providing and running
binary code of their choosing on the BIG-IP platform. This raises a high bar
for attackers attempting to target BIG-IP systems over a network and would
require an additional, un-patched, user-space remote code execution
vulnerability to exploit these new issues.

The only Administrative Roles on a BIG-IP system that can run binary code or
exploitable analogs, such as JavaScript, are the Administrator, Resource
Administrator, Manager, and iRules Manager roles. The Administrator and
Resource Administrator users already have nearly complete access to the system
and all secrets on the system that are not protected by hardware-based
encryption. The Manager and iRules Manager roles have more restricted access to
the system but can install new iRulesLX code. A malicious, authorized Manager
or iRules Manager could install malicious binary code to exploit these
information leaks and gain more privileged access. F5 recommends that you limit
access to these roles to only trusted employees.

F5 believes that BIG-IP virtual editions running as guests on a public or
private cloud infrastructure are no more vulnerable than any other Linux-based
guest. You must patch the host hypervisor to mitigate these issues for the
host, and to mitigate issues between guests. There are currently no known fixes
for Linux-based products that would protect such a guest from another malicious
guest on the same host, in regard to these issues; however, the Spectre 1 and
Meltdown mitigations might help protect a given guest's kernel-space from an
attack launched by a user-space process on that guest.

F5 believes that the attack with the highest realistic impact may occur in
multi-tenancy Virtual Clustered Multiprocessing (vCMP) configurations, as
follows:

  o Meltdown and Spectre variant 1 might allow an attacker in one
    administrative domain to collect privileged information from the host or
    guests owned by another administrative domain. Exploiting these attacks
    would be significantly more difficult on the BIG-IP system than on a
    standard Linux-based system due to BIG-IP system memory and process
    scheduling architecture.
  o Spectre variant 2 might allow an attacker in one administrative domain to
    collect privileged information from the host or guests owned by another
    administrative domain, as long as the attacker's guest is configured as a
    single-core guest. The BIG-IP system always maps both hyper-threads of a
    given core to any guest with the Cores Per Guest configuration set to 2 or
    more, but single-core guests may run on the same processor core as another
    single-core guest or host code. This threat may be mitigated by ensuring
    that all guests are set to at least two Cores Per Guest.

F5 is currently researching and implementing fixes for supported releases and
will update this article as those releases are scheduled. At this time, F5
believes that adding fixes for these issues to existing Engineering HotFixes
may be unfeasible due to the magnitude of the changes required.

To determine which vulnerabilities affect each platform and the processor type
each platform uses, refer to the following table.

Note: In the following table, only one entry is shown for platform models that
may have several variants. For example, BIG-IP 11000, BIG-IP 11050, BIG-IP
11050F, and BIG-IP 11050N are all vulnerable and included in the table as
"BIG-IP 110x0". Some platforms may have multiple vendor processors, such as the
iSeries platforms, which have one or more Intel core processors and may have a
vulnerable ARM processor in one or more subsystems. F5 does not believe that
ARM processors in these subsystems are accessible to attackers, unless some
other code-execution vulnerability is present, but the information is being
provided out of an abundance of caution.

+-------------+---------+------------------+------------------+---------------+
|             |Processor|Vulnerable to     |Vulnerable to     |Vulnerable to  |
|Model        |Type     |CVE-2017-5753     |CVE-2017-5715     |CVE-2017-5754  |
|             |         |Spectre Variant 1 |Spectre Variant 2 |Meltdown       |
+-------------+---------+------------------+------------------+---------------+
|VIPRION B21x0|Intel    |Y                 |Y                 |Y              |
+-------------+---------+------------------+------------------+---------------+
|VIPRION B2250|Intel    |Y                 |Y                 |Y              |
+-------------+---------+------------------+------------------+---------------+
|VIPRION B4100|AMD      |**                |**                |**             |
+-------------+---------+------------------+------------------+---------------+
|VIPRION B4200|AMD      |**                |**                |**             |
+-------------+---------+------------------+------------------+---------------+
|VIPRION B43x0|Intel    |Y                 |Y                 |Y              |
+-------------+---------+------------------+------------------+---------------+
|VIPRION B44x0|Intel    |Y                 |Y                 |Y              |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 800   |Intel    |**                |**                |**             |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 1600  |Intel    |**                |**                |**             |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 3600  |Intel    |**                |**                |**             |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 3900  |Intel    |**                |**                |**             |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 6400  |Intel    |**                |**                |**             |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 2xx0  |Intel    |Y                 |Y                 |Y              |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 4xx0  |Intel    |Y                 |Y                 |Y              |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 5xx0  |Intel    |Y                 |Y                 |Y              |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 7xx0  |Intel    |Y                 |Y                 |Y              |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 10xx0 |Intel    |Y                 |Y                 |Y              |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 12xx0 |Intel    |Y                 |Y                 |Y              |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP i2x00 |Intel,   |Y                 |Y                 |Y              |
|             |ARM      |                  |                  |               |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP i4x00 |Intel,   |Y                 |Y                 |Y              |
|             |ARM      |                  |                  |               |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP i5x00 |Intel,   |Y                 |Y                 |Y              |
|             |ARM      |                  |                  |               |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP i7x00 |Intel,   |Y                 |Y                 |Y              |
|             |ARM      |                  |                  |               |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP i10x00|Intel,   |Y                 |Y                 |Y              |
|             |ARM      |                  |                  |               |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 6900  |AMD      |Y                 |N                 |N              |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 89x0  |AMD      |Y                 |N                 |N              |
+-------------+---------+------------------+------------------+---------------+
|BIG-IP 110x0 |AMD      |Y                 |N                 |N              |
+-------------+---------+------------------+------------------+---------------+

**Confirmation of vulnerability or non-vulnerability is not presently
available. F5 is still researching the issue for the models indicated and will
update this article with the most current information as soon as it has been
confirmed. F5 Technical Support has no additional information on this issue.

Note: Platform models that have reached End of Technical Support (EoTS) will
not be evaluated. For more information, refer to K4309: F5 platform lifecycle
support policy.

Traffix

Systems with microprocessors that use speculative execution and indirect branch
prediction may allow unauthorized disclosure of information to an attacker with
local user access via a side-channel analysis.

Security Advisory Status

F5 Product Development has assigned 698651, 701445, and 701447 (BIG-IP);
 702233, 702236, and 202237 (BIG-IQ); 702353, 702354, and 702355 (Enterprise
Manager); 702355, 702377, and 702378 (iWorkflow); CPF-24782, CPF-24783, and
CPF-24784 (Traffix) 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 or hotfixes that
address the vulnerability, refer to the following table.

+---------------+------+----------+----------+---------------+-----------------+----------+
|               |      |Versions  |Fixes     |               |                 |Vulnerable|
|Product        |Branch|known to  |introduced|Severity       |CVSSv3 score^1   |component |
|               |      |be        |in        |               |                 |or feature|
|               |      |vulnerable|          |               |                 |          |
+---------------+------+----------+----------+---------------+-----------------+----------+
|BIG-IP (LTM,   |13.x  |13.1.0    |None      |               |                 |          |
|AAM, AFM,      |      |13.0.0    |          |               |                 |          |
|Analytics, APM,+------+----------+----------+               |                 |          |
|ASM, DNS, Edge |12.x  |12.1.0 -  |None      |               |                 |          |
|Gateway,       |      |12.1.3    |          |               |                 |CPU, BIOS,|
|GTM, Link      +------+----------+----------+Medium         |6.4              |and kernel|
|Controller,    |      |11.6.1 -  |          |               |                 |          |
|PEM,           |      |11.6.2    |          |               |                 |          |
|WebAccelerator,|11.x  |11.5.1 -  |None      |               |                 |          |
|WebSafe)       |      |11.5.5    |          |               |                 |          |
|               |      |11.2.1    |          |               |                 |          |
+---------------+------+----------+----------+---------------+-----------------+----------+
|ARX            |6.x   |**        |**        |**             |**               |**        |
+---------------+------+----------+----------+---------------+-----------------+----------+
|               |      |          |          |Medium         |                 |          |
|               |      |          |          |(CVE-2017-5715)|6.4 CVE-2017-5715|          |
|Enterprise     |3.x   |**        |None      |Medium         |5.3 CVE-2017-5753|CPU, BIOS,|
|Manager        |      |          |          |(CVE-2017-5753)|6.4 CVE-2017-5754|and kernel|
|               |      |          |          |Medium         |                 |          |
|               |      |          |          |(CVE-2017-5754)|                 |          |
+---------------+------+----------+----------+---------------+-----------------+----------+
|               |      |          |          |Medium         |                 |          |
|BIG-IQ (Cloud, |      |          |          |(CVE-2017-5715)|6.4 CVE-2017-5715|          |
|Device,        |4.x   |**        |None      |Medium         |5.3 CVE-2017-5753|CPU, BIOS,|
|Security, ADC) |      |          |          |(CVE-2017-5753)|6.4 CVE-2017-5754|and kernel|
|               |      |          |          |Medium         |                 |          |
|               |      |          |          |(CVE-2017-5754)|                 |          |
+---------------+------+----------+----------+---------------+-----------------+----------+
|               |      |          |          |Medium         |                 |          |
|               |5.x   |**        |None      |(CVE-2017-5715)|                 |          |
|BIG-IQ         |      |          |          |Medium         |6.4 CVE-2017-5715|CPU, BIOS,|
|Centralized    +------+----------+----------+(CVE-2017-5753)|5.3 CVE-2017-5753|and kernel|
|Management     |      |          |          |Medium         |6.4 CVE-2017-5754|          |
|               |4.x   |**        |None      |(CVE-2017-5754)|                 |          |
|               |      |          |          |               |                 |          |
+---------------+------+----------+----------+---------------+-----------------+----------+
|               |      |          |          |Medium         |                 |          |
|BIG-IQ Cloud   |      |          |          |(CVE-2017-5715)|6.4 CVE-2017-5715|          |
|and            |1.x   |**        |None      |Medium         |5.3 CVE-2017-5753|CPU, BIOS,|
|Orchestration  |      |          |          |(CVE-2017-5753)|6.4 CVE-2017-5754|and kernel|
|               |      |          |          |Medium         |                 |          |
|               |      |          |          |(CVE-2017-5754)|                 |          |
+---------------+------+----------+----------+---------------+-----------------+----------+
|               |      |          |          |Medium         |                 |          |
|               |      |          |          |(CVE-2017-5715)|6.4 CVE-2017-5715|          |
|F5 iWorkflow   |2.x   |**        |None      |Medium         |5.3 CVE-2017-5753|CPU, BIOS,|
|               |      |          |          |(CVE-2017-5753)|6.4 CVE-2017-5754|and kernel|
|               |      |          |          |Medium         |                 |          |
|               |      |          |          |(CVE-2017-5754)|                 |          |
+---------------+------+----------+----------+---------------+-----------------+----------+
|LineRate       |2.x   |**        |**        |**             |**               |**        |
+---------------+------+----------+----------+---------------+-----------------+----------+
|               |5.x   |5.1.0     |None      |Medium         |6.7              |          |
|               |      |          |          |(CVE-2017-5715)|(CVE-2017-5715)  |          |
|Traffix SDC    +------+----------+----------+High           |8.2              |CPU, BIOS,|
|               |      |4.0.0 -   |          |(CVE-2017-5753)|(CVE-2017-5753)  |and kernel|
|               |4.x   |4.4.0     |None      |High           |7.9              |          |
|               |      |          |          |(CVE-2017-5754)|(CVE-2017-5754)  |          |
+---------------+------+----------+----------+---------------+-----------------+----------+

**Confirmation of vulnerability or non-vulnerability is not presently
available. F5 is still researching the issue for the products indicated and
will update this article with the most current information as soon as it has
been confirmed. F5 Technical Support has no additional information on this
issue.

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

Security Advisory Recommended Actions

If you are running a version listed in the Versions known to be vulnerable
column, you can eliminate this vulnerability by upgrading to a version listed
in the Fixes introduced in column. If the table lists only an older version
than what you are currently running, or does not list a non-vulnerable version,
then no upgrade candidate currently exists.

Note: For details about how Security Advisory articles are versioned, and what
versions are listed in the table, refer to K51812227: Understanding Security
Advisory versioning.

Mitigation

To mitigate the Spectre Variant 2 vulnerability in a multi-tenancy vCMP
configuration, running single-core guests owned by different administrative
domains, you can set the "Cores Per Guest" configuration to 2 or more for all
guests.

Supplemental Information

  o https://googleprojectzero.blogspot.ca/2018/01/
    reading-privileged-memory-with-side.html

    Note: This link takes you to a resource outside of AskF5. The third party
    could remove the document without our knowledge.

  o https://meltdownattack.com/

    Note: This link takes you to a resource outside of AskF5. The third party
    could remove the document without our knowledge.

  o K9970: Subscribing to email notifications regarding F5 products
  o K9957: Creating a custom RSS feed to view new and updated documents
  o K4602: Overview of the F5 security vulnerability response policy
  o K4918: Overview of the F5 critical issue hotfix policy

Applies to (see versions):

  o ARX:
       6.4.0, 6.3.0, 6.2.0
  o BIG-IP AAM:
       13.1.0, 13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.2, 11.6.1,
        11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.3.0, 11.2.1
  o BIG-IP AFM:
       13.1.0, 13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.2, 11.6.1,
        11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.3.0, 11.2.1
  o BIG-IP APM:
       13.1.0, 13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.2, 11.6.1,
        11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.3.0, 11.2.1
  o BIG-IP ASM:
       13.1.0, 13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.2, 11.6.1,
        11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.3.0, 11.2.1
  o BIG-IP Analytics:
       13.1.0, 13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.2, 11.6.1,
        11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.3.0, 11.2.1
  o BIG-IP DNS:
       13.1.0, 13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.2, 11.6.1,
        11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.3.0, 11.2.1
  o BIG-IP Edge Gateway:
       13.1.0, 13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.2, 11.6.1,
        11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.3.0, 11.2.1
  o BIG-IP GTM:
       13.1.0, 13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.2, 11.6.1,
        11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.3.0, 11.2.1
  o BIG-IP LTM:
       13.1.0, 13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.2, 11.6.1,
        11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.3.0, 11.2.1
  o BIG-IP Link Controller:
       13.1.0, 13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.2, 11.6.1,
        11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.3.0, 11.2.1
  o BIG-IP PEM:
       13.1.0, 13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.2, 11.6.1,
        11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.3.0, 11.2.1
  o BIG-IP WebAccelerator:
       13.1.0, 13.0.0, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.2, 11.6.1,
        11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.3.0, 11.2.1
  o BIG-IQ ADC:
       5.4.0, 5.3.0, 5.2.0, 5.1.0, 5.0.0, 4.6.0, 4.5.0, 4.4.0
  o BIG-IQ Centralized Management:
       5.4.0, 5.3.0, 5.2.0, 5.1.0, 5.0.0, 4.6.0, 4.5.0, 4.4.0
  o BIG-IQ Cloud:
       5.4.0, 5.3.0, 5.2.0, 5.1.0, 5.0.0, 4.6.0, 4.5.0, 4.4.0
  o BIG-IQ Cloud and Orchestration:
       1.0.0
  o BIG-IQ Device:
       5.4.0, 5.3.0, 5.2.0, 5.1.0, 5.0.0, 4.6.0, 4.5.0, 4.4.0
  o BIG-IQ Security:
       5.4.0, 5.3.0, 5.2.0, 5.1.0, 5.0.0, 4.6.0, 4.5.0, 4.4.0
  o Enterprise Manager:
       3.1.1
  o F5 MobileSafe:
       1.0.0
  o F5 WebSafe:
       1.0.0
  o F5 iWorkflow:
       2.0.0, 2.1.0, 2.0.1, 2.2.0, 2.0.2, 2.3.0
  o LineRate:
       2.6.2, 2.6.0, 2.5.1, 2.6.1, 2.5.2, 2.5.0
  o Traffix SDC:
       4.0.2, 5.1.0, 4.0.0, 4.4.0, 4.0.5

- --------------------------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

iQIVAwUBWmU1Box+lLeg9Ub1AQj0qw/+JYG8FGea8flts2RII06e54gqRBPGsmK9
lcGzGQxPKtOU3GSF2BjXIVh2WWnwpAdTcjD3Lxrv181B5ULNCg+W4cmU27GZjVs1
MO6JFp74bDCoQ5x3G6Cd8sqGjz8s4x26CF/KygkyBgH6mQQZZl/0Y4+ABbXoSMF+
tV9gm67EHR6bKC1f2DqSqeom1AlVXcYleRFZdaNANPAej8p741Mj2TgkonrllT+J
VCnKeW+KcbfVA8kxTEfYU0Hgba5kEr1IxPhqkdt+Js/LP72sAPNGRamCAEcShO1T
2QUC539KXgS/vECCSGgl+iSucj0VdOAkBbVZyvdomCnLEV7PdhF8yfIdZ1TqRJVx
ncoZFYkCSHJKJ9O1nwg7Pkt7IedymQkTgM0ruOG0iK8YSfuJ/fjkr3OkWyVSk0Ro
B49tD3LdaLCWz44EYf7CR90hBu6eeBjbBnZLTEKXHZw2NZgUc1YsltVOdjKwzjlE
MKCZIvdjPl9D4fIsi8D0TFI3FsPkUGGBjhgIjdKdJyMor6/Y0DUKwKvO/inWsICt
sWLEFwdBA0noG6WssXvhZVbMYIbFCVnZrERabvSfTid6EU347xksxM79s2WO9jBn
KiYyjeV/cnI8DttWxfJKVz3pOxwhHDmipmRjVy0CHekAXfKOPqY3ZbOs3oEtEw/n
nteHYUJt7B0=
=Na7u
-----END PGP SIGNATURE-----

« Back to bulletins