Malware Devil

Monday, March 15, 2021

ESB-2021.0904 – [SUSE] stunnel: Unauthorised access – Remote/unauthenticated

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

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

                               ESB-2021.0904
                        Security update for stunnel
                               15 March 2021

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

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

Product:           stunnel
Publisher:         SUSE
Operating System:  SUSE
Impact/Access:     Unauthorised Access -- Remote/Unauthenticated
Resolution:        Patch/Upgrade
CVE Names:         CVE-2021-20230  

Reference:         ESB-2021.0662

Original Bulletin: 
   https://www.suse.com/support/update/announcement/2021/suse-su-20210772-1

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

SUSE Security Update: Security update for stunnel

______________________________________________________________________________

Announcement ID:   SUSE-SU-2021:0772-1
Rating:            important
References:        #1177580 #1182529
Cross-References:  CVE-2021-20230
Affected Products:
                   SUSE Linux Enterprise Module for Server Applications 15-SP2
______________________________________________________________________________

An update that solves one vulnerability and has one errata is now available.

Description:

This update for stunnel fixes the following issues:

  o Security fix: [bsc#1177580, bsc#1182529, CVE-2021-20230] * "redirect"
    option does not properly handle "verifyChain = yes"

Patch Instructions:

To install this SUSE Security Update use the SUSE recommended installation
methods like YaST online_update or "zypper patch".
Alternatively you can run the command listed for your product:

  o SUSE Linux Enterprise Module for Server Applications 15-SP2:
    zypper in -t patch SUSE-SLE-Module-Server-Applications-15-SP2-2021-772=1

Package List:

  o SUSE Linux Enterprise Module for Server Applications 15-SP2 (aarch64
    ppc64le s390x x86_64):
       stunnel-5.57-3.11.1
       stunnel-debuginfo-5.57-3.11.1
       stunnel-debugsource-5.57-3.11.1


References:

  o https://www.suse.com/security/cve/CVE-2021-20230.html
  o https://bugzilla.suse.com/1177580
  o https://bugzilla.suse.com/1182529

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

iQIVAwUBYE7lduNLKJtyKPYoAQg7hQ//Zw8hpOXy+SJD7BiRSm5/t0DmGj05dUPp
zLVynTvYRRTiNfjfXBN9jKMCaoDn6xFvsq2z6ny5+iD4ln50o6asvXYHdA3LFZno
gde4Gnq5svYpW7xT7h8qR4MJ/jgCOcc/BqzBHWxH4IemsTsieJ1VZPiJQyKC5sD+
MG3PKym0PMmUc+RHXeavr+ejleqChOUm+GHsPyKlHcTwON8fyOlh8ftJQ2HG/JJS
eVNImUUKZWanS6UvyKVZifpRX/k9sp4behBqMkFbLDYFj7buUIcA0PwX+TzbtTI3
8FFt8Rf8xuqHz489NgzIBvDnBdZej5x4F1fbaaE7aWVwq4Db2M7YMFJoBRcqUNdt
on+gnifekVeM5Bw1HtjyUs+gr3Jxq05U9+s9GYf7xHkoPVppiQMsmqMsyK4ZmtD4
iRokS8CHKoeJa8SIf3iCdNn8xv2gObPhC72fIkbvWDwWfQiGf6zA7Rq5oCKLguQq
12n/pEd1OvHIDxdiKTgurp6ez9HollqMtd3T2JsfzdhEa9tBpszLbM0214/QpJFB
h9tBGr1h81V7uSOQsE8DC68Dir0fGcjH1uh1oslNsVBul1Mi5l84cTXcINEOveDz
8hf6WVkyNA71xvUVfrb86+wrnUgSGib7W0gchz7ZsCu8bhkiAPFUUeUfBsSZBgvZ
/fmaqWJLaTI=
=H1UQ
-----END PGP SIGNATURE-----

Read More

The post ESB-2021.0904 – [SUSE] stunnel: Unauthorised access – Remote/unauthenticated appeared first on Malware Devil.



https://malwaredevil.com/2021/03/15/esb-2021-0904-suse-stunnel-unauthorised-access-remote-unauthenticated/?utm_source=rss&utm_medium=rss&utm_campaign=esb-2021-0904-suse-stunnel-unauthorised-access-remote-unauthenticated

ESB-2021.0872.2 – UPDATED ALERT [Appliance] BIG-IP Products: Multiple vulnerabilities

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

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

                              ESB-2021.0872.2
                Advanced WAF/ASM - Multple Vulnerabilities
                               15 March 2021

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

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

Product:           BIG-IP Products
Publisher:         F5 Networks
Operating System:  Network Appliance
Impact/Access:     Root Compromise                 -- Remote/Unauthenticated      
                   Execute Arbitrary Code/Commands -- Remote/Unauthenticated      
                   Create Arbitrary Files          -- Existing Account            
                   Denial of Service               -- Remote/Unauthenticated      
                   Cross-site Scripting            -- Remote with User Interaction
Resolution:        Patch/Upgrade
CVE Names:         CVE-2021-23001 CVE-2021-22993 CVE-2021-22992
                   CVE-2021-22990 CVE-2021-22989 CVE-2021-22988
                   CVE-2021-22987 CVE-2021-22986 

Original Bulletin: 
   https://support.f5.com/csp/article/K45056101
   https://support.f5.com/csp/article/K52510511
   https://support.f5.com/csp/article/K55237223
   https://support.f5.com/csp/article/K06440657

Comment: This bulletin contains four (4) F5 Networks security advisories.

Revision History:  March 15 2021: Added multiple BIG-IP Products for K52510511
                   March 11 2021: Initial Release

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

K45056101: Advanced WAF/ASM TMUI authenticated remote command execution
vulnerability CVE-2021-22990

Original Publication Date: 11 Mar, 2021

Security Advisory Description

On systems with Advanced WAF or BIG-IP ASM provisioned, the Traffic Management
User Interface (TMUI), also referred to as the Configuration utility, has an
authenticated remote command execution vulnerability in undisclosed pages. (
CVE-2021-22990)

Note: For systems running in Appliance mode, refer to K56142644 Appliance Mode
Advanced WAF/ASM TMUI authenticated remote command execution vulnerability
CVE-2021-22989.

Impact

This vulnerability allows highly privileged authenticated users with the roles
Administrator, Resource Administrator, or Application Security Administrator
with network access to the Configuration utility, through the BIG-IP management
port or self IP addresses, to execute arbitrary system commands, create and
delete files, or disable services. This vulnerability can only be exploited
through the control plane and cannot be exploited through the data plane.
Exploitation can lead to complete system compromise.

Note: If you believe your system may have been compromised, refer to K11438344:
Considerations and guidance when you suspect a security compromise on a BIG-IP
system.

Security Advisory Status

F5 Product Development has assigned ID 953729 (BIG-IP) 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.

+-------------+------+-------------+----------+----------+------+-------------+
|             |      |Versions     |Fixes     |          |CVSSv3|Vulnerable   |
|Product      |Branch|known to be  |introduced|Severity  |score^|component or |
|             |      |vulnerable   |in        |          |1     |feature      |
+-------------+------+-------------+----------+----------+------+-------------+
|             |16.x  |16.0.0 -     |16.0.1.1  |          |      |             |
|             |      |16.0.1       |          |          |      |             |
|             +------+-------------+----------+          |      |             |
|             |15.x  |15.1.0 -     |15.1.2.1  |          |      |             |
|             |      |15.1.2       |          |          |      |             |
|             +------+-------------+----------+          |      |             |
|             |14.x  |14.1.0 -     |14.1.4    |          |      |             |
|BIG-IP       |      |14.1.3       |          |          |      |TMUI/        |
|(Advanced WAF+------+-------------+----------+Medium    |6.6   |Configuration|
|and ASM)     |13.x  |13.1.0 -     |13.1.3.6  |          |      |utility      |
|             |      |13.1.3       |          |          |      |             |
|             +------+-------------+----------+          |      |             |
|             |12.x  |12.1.0 -     |12.1.5.3  |          |      |             |
|             |      |12.1.5       |          |          |      |             |
|             +------+-------------+----------+          |      |             |
|             |11.x  |11.6.1 -     |11.6.5.3  |          |      |             |
|             |      |11.6.5       |          |          |      |             |
+-------------+------+-------------+----------+----------+------+-------------+
|             |8.x   |None         |Not       |          |      |             |
|             |      |             |applicable|          |      |             |
|BIG-IQ       +------+-------------+----------+          |      |             |
|Centralized  |7.x   |None         |Not       |Not       |None  |None         |
|Management   |      |             |applicable|vulnerable|      |             |
|             +------+-------------+----------+          |      |             |
|             |6.x   |None         |Not       |          |      |             |
|             |      |             |applicable|          |      |             |
+-------------+------+-------------+----------+----------+------+-------------+
|F5OS         |1.x   |None         |Not       |Not       |None  |None         |
|             |      |             |applicable|vulnerable|      |             |
+-------------+------+-------------+----------+----------+------+-------------+
|Traffix SDC  |5.x   |None         |Not       |Not       |None  |None         |
|             |      |             |applicable|vulnerable|      |             |
+-------------+------+-------------+----------+----------+------+-------------+

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

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 table does not list a fixed version for
your software 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. Refer to 
K51812227: Understanding security advisory versioning.

If you are using public cloud marketplaces (AWS, Azure, GCP, or Alibaba) to
deploy BIG-IP Virtual Edition (VE), F5 recommends that you install the latest
releases of BIG-IP versions listed in the Fixes introduced in column, subject
to their availability on those marketplaces. For more information, refer to the
following articles:

  o BIG-IP VE Supported Platforms
  o K84205182: BIG-IP upgrade guide | Chapter 1: Guide contents

Mitigation

As this attack is conducted by legitimate, authenticated users, there is no
viable mitigation while still allowing the user access to the Configuration
utility. The only mitigation is to remove access for any users who are not
completely trusted.

Until it is possible to install a fixed version, you can use the following
sections as temporary mitigations. These mitigations restrict access to the
Configuration utility to only trusted networks or devices, thereby limiting the
attack surface.

  o Block Configuration utility access through self IP addresses
  o Block Configuration utility access through the management interface

Block Configuration utility access through self IP addresses

You can block all access to the Configuration utility of your BIG-IP system
using self IP addresses. To do so, you can change the Port Lockdown setting to
Allow None for each self IP address on the system. If you must open any ports,
you should use the Allow Custom option, taking care to disallow access to the
Configuration utility. By default, the Configuration utility listens on TCP
port 443. Alternatively, you can configure a custom port.

Note: Performing this action prevents all access to the Configuration utility
and iControl REST using the self IP address. These changes may also impact
other services, including breaking high availability (HA) configurations.

Before you make changes to the configuration of your self-IP addresses, F5
strongly recommends that you refer to the following articles:

  o K17333: Overview of port lockdown behavior (12.x - 16.x)
  o K13092: Overview of securing access to the BIG-IP system
  o K31003634: The Configuration utility of the Single-NIC BIG-IP Virtual
    Edition now defaults to TCP port 8443
  o K51358480: The single-NIC BIG-IP VE may erroneously revert to the default
    management httpd port after a configuration reload

Block Configuration utility access through the management interface

To mitigate this vulnerability for affected F5 products, you should restrict
management access only to trusted users and devices to F5 products over a
secure network. For more information about securing access to BIG-IP systems,
refer to the following articles:

  o K13309: Restricting access to the Configuration utility by source IP
    address (11.x - 16.x)
  o K13092: Overview of securing access to the BIG-IP system
  o K46122561: Restricting access to the management interface using network
    firewall rules

Supplemental Information

o K02566623: Overview of F5 critical vulnerabilities (March 2021)
  o K04532512: Frequently asked questions for CVE-2021-22986, CVE-2021-22987,
    CVE-2021-22988, CVE-2021-22989, and CVE-2021-22990
  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 K9502: BIG-IP hotfix and point release matrix
  o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
  o K48955220: Installing an OPSWAT Endpoint Security update on BIG-IP APM
    systems (11.4.x and later)
  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

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

K52510511: Advanced WAF/ASM buffer-overflow vulnerability CVE-2021-22992

Original Publication Date: 11 Mar, 2021
Latest   Publication Date: 13 Mar, 2021

Security Advisory Description

A malicious HTTP response to an Advanced WAF/ASM virtual server with Login Page
configured in its policy may trigger a buffer overflow, resulting in a DoS
attack. In certain situations, it may allow remote code execution (RCE),
leading to complete system compromise. (CVE-2021-22992)

Impact

A sophisticated attacker must have control over the back-end web servers (pool
members) or the ability to manipulate the server-side HTTP responses to the
virtual server to exploit this vulnerability. With this level of back-end
control, the attacker may cause the BIG-IP Advanced WAF/ASM system to
experience a denial-of-service (DoS). In the worst case, the attacker may
execute arbitrary code on the BIG-IP Advanced WAF/ASM system. This
vulnerability can only be exploited through the data plane and cannot be
exploited through the control plane. Exploitation can lead to complete system
compromise.

Note: If you believe your system may have been compromised, refer to K11438344:
Considerations and guidance when you suspect a security compromise on a BIG-IP
system.

Security Advisory Status

F5 Product Development has assigned ID 975233 (BIG-IP) 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.

+-------------------+------+----------+----------+----------+------+----------+
|                   |      |Versions  |Fixes     |          |CVSSv3|Vulnerable|
|Product            |Branch|known to  |introduced|Severity  |score^|component |
|                   |      |be        |in        |          |1     |or feature|
|                   |      |vulnerable|          |          |      |          |
+-------------------+------+----------+----------+----------+------+----------+
|                   |16.x  |16.0.0 -  |16.0.1.1  |          |      |          |
|                   |      |16.0.1    |          |          |      |          |
|                   +------+----------+----------+          |      |          |
|                   |15.x  |15.1.0 -  |15.1.2.1  |          |      |          |
|                   |      |15.1.2    |          |          |      |          |
|                   +------+----------+----------+          |      |          |
|                   |14.x  |14.1.0 -  |14.1.4    |          |      |          |
|BIG-IP (Advanced   |      |14.1.3    |          |          |      |ASM       |
|WAF and ASM)       +------+----------+----------+Critical  |9.0   |virtual   |
|                   |13.x  |13.1.0 -  |13.1.3.6  |          |      |server    |
|                   |      |13.1.3    |          |          |      |          |
|                   +------+----------+----------+          |      |          |
|                   |12.x  |12.1.0 -  |12.1.5.3* |          |      |          |
|                   |      |12.1.5    |          |          |      |          |
|                   +------+----------+----------+          |      |          |
|                   |11.x  |11.6.1 -  |11.6.5.3  |          |      |          |
|                   |      |11.6.5    |          |          |      |          |
+-------------------+------+----------+----------+----------+------+----------+
|                   |16.x  |None      |Not       |          |      |          |
|                   |      |          |applicable|          |      |          |
|                   +------+----------+----------+          |      |          |
|                   |15.x  |None      |Not       |          |      |          |
|                   |      |          |applicable|          |      |          |
|BIG-IP (LTM, AAM,  +------+----------+----------+          |      |          |
|AFM, Analytics,    |14.x  |None      |Not       |          |      |          |
|APM, DDHD, DNS,    |      |          |applicable|Not       |      |          |
|FPS, GTM, Link     +------+----------+----------+vulnerable|None  |None      |
|Controller, PEM,   |13.x  |None      |Not       |          |      |          |
|SSLO)              |      |          |applicable|          |      |          |
|                   +------+----------+----------+          |      |          |
|                   |12.x  |None      |Not       |          |      |          |
|                   |      |          |applicable|          |      |          |
|                   +------+----------+----------+          |      |          |
|                   |11.x  |None      |Not       |          |      |          |
|                   |      |          |applicable|          |      |          |
+-------------------+------+----------+----------+----------+------+----------+
|                   |8.x   |None      |Not       |          |      |          |
|                   |      |          |applicable|          |      |          |
|                   +------+----------+----------+          |      |          |
|BIG-IQ Centralized |7.x   |None      |Not       |Not       |None  |None      |
|Management         |      |          |applicable|vulnerable|      |          |
|                   +------+----------+----------+          |      |          |
|                   |6.x   |None      |Not       |          |      |          |
|                   |      |          |applicable|          |      |          |
+-------------------+------+----------+----------+----------+------+----------+
|F5OS               |1.x   |None      |Not       |Not       |None  |None      |
|                   |      |          |applicable|vulnerable|      |          |
+-------------------+------+----------+----------+----------+------+----------+
|Traffix SDC        |5.x   |None      |Not       |Not       |None  |None      |
|                   |      |          |applicable|vulnerable|      |          |
+-------------------+------+----------+----------+----------+------+----------+

*An issue with the bigd process has been discovered in version 12.1.5.3. For
more information, refer to K50524736: Bigd process memory leak after updating
to BIG-IP 12.1.5.3.

The 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 table does not list a fixed version for
your software 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.  Refer to 
K51812227: Understanding security advisory versioning.

If you are using public cloud marketplaces (AWS, Azure, GCP, or Alibaba) to
deploy BIG-IP Virtual Edition (VE), F5 recommends that you install the latest
releases of BIG-IP versions listed in the Fixes introduced in column, subject
to their availability on those marketplaces. For more information, refer to the
following articles:

  o BIG-IP VE Supported Platforms
  o K84205182: BIG-IP upgrade guide | Chapter 1: Guide contents

Mitigation

  o Mitigate malicious connections using an iRule
  o Modify Login Page configuration
  o Harden pool members
  o Remove Login Pages

Mitigate malicious connections using an iRule

To mitigate this vulnerability, you can associate the following iRule with the
affected virtual servers. The iRule examines the response from the server and
returns a 502 error for vulnerable responses. To use the iRule mitigation,
perform the following procedure:

Impact of workaround: The following mitigation may add additional resource load
on the system, depending on the specific environment. F5 recommends that you
test any such changes during a maintenance window and consider the possible
impact on your environment.

 1. Log in to the Configuration utility.
 2. Go to Local Traffic > iRules > iRule List.
 3. Select Create.
 4. Enter a name for the iRule.
 5. For Definition, add the following iRule code:

    # Mitigation for K52510511: Advanced WAF/ASM Buffer Overflow vulnerability
    CVE-2021-22992
    when RULE_INIT {
    # Set static::debug 1 to enable debug logging.
        set static::debug 0
        set static::max_length 4000
    }
    when HTTP_REQUEST {
        if {$static::debug}{
            set LogString "Client [IP::client_addr]:[TCP::client_port] ->
    [HTTP::host][HTTP::uri]"
    }
            set uri [string tolower [HTTP::uri]]
    }
    when HTTP_RESPONSE {
        set header_names [HTTP::header names]
        set combined_header_name [join $header_names ""]
        set combined_header_name_len [string length $combined_header_name]
        if {$static::debug}{
            log local0. "=================response======================"
            log local0. "$LogString (response)"
            log local0. "combined header names: $combined_header_name"
            foreach aHeader [HTTP::header names] {
            log local0. "$aHeader: [HTTP::header value $aHeader]"
    }
            log local0. "the length of the combined response header names:
    $combined_header_name_len"
            log local0. "============================================="
    }
        if { ( $combined_header_name_len > $static::max_length ) } {
            log local0. "In the response of '$uri', the length of the combined
    header names $combined_header_name_len exceeds the maximum value
    $static::max_length. See K52510511: Advanced WAF/ASM Buffer Overflow
    vulnerability CVE-2021-22992"
    HTTP::respond 502 content "
Bad Gateway
    
The server response is invalid. Please inform the administrator. Error: K52510511" } } 6. Select Finished. 7. Associate the iRule with the affected virtual servers. Modify Login Page configuration To mitigate this vulnerability, you may remove the configuration of both of the following settings from the Login Page configuration: o Expected validation header name and value o Not expected validation header name and value To do so, perform the following procedure: 1. Log in to the Configuration utility of the affected BIG-IP Advanced WAF/ASM system. 2. Go to Security > Application Security > Sessions and Logins > Login Pages List. 3. Select the security policy from the Current edited policy list. 4. Select the name of the Login URL from the Login Pages List. 5. Remove all configuration from both the settings. 6. Select Save to save the changes. 7. Select Apply Policy to apply the changes. 8. Select OK to confirm the operation. These two settings should remain empty until the affected BIG-IP Advanced WAF/ ASM system is updated to a version listed in the Fixes introduced in column. Important: You may need to configure alternative Login Page access validation criteria to continue using the Login Page without these set. Harden pool members To mitigate this vulnerability, you can harden your back-end web servers and network to prevent the malicious headers in the HTTP response to the login page from being sent to the BIG-IP Advanced WAF/ASM system. Other attacks against the server, such as CRLF Injection or HTTP Response Splitting, may also be used to manipulate the HTTP response. Use of HTTP protocol compliance can protect against these attacks, refer to K10280: Overview of BIG-IP ASM HTTP protocol compliance. Remove Login Pages Alternatively, you can delete any Login Page configured for a security policy and avoid using the Login Page feature until the affected BIG-IP Advanced WAF/ ASM system is upgraded to a version listed in the Fixes introduced in column. To delete a login page, perform the following procedure: 1. Login to the Configuration utility of the affected BIG-IP ASM system. 2. Go to Security > Application Security > Sessions and Logins > Login Pages List. 3. Select the security policy from the Current edited policy list. 4. Select the login page configuration you want to remove. 5. Select Delete. 6. Select OK to confirm the deletion. 7. Select Apply Policy to apply the changes. 8. Select OK to confirm the operation. Important: Login Page configuration may be critical to the function of the Brute Force Attack Prevention, Login Enforcement, and Session Tracking functions in a security policy. Review your security policy to see if any of these functions require the Login Page configuration before deleting it. Acknowledgements F5 acknowledges Felix Wilhelm of Google Project Zero for bringing this issue to our attention and following the highest standards of coordinated disclosure. Supplemental Information o K02566623: Overview of F5 critical vulnerabilities (March 2021) o K50963210: Frequently asked questions for CVE-2021-22992 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 K9502: BIG-IP hotfix and point release matrix o K13123: Managing BIG-IP product hotfixes (11.x - 16.x) o K15106: Managing BIG-IQ product hotfixes o K15113: BIG-IQ hotfix and point release matrix o K48955220: Installing an OPSWAT Endpoint Security update on BIG-IP APM systems (11.4.x and later) 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 - ------------------------------------------------------------------------------- K55237223: BIG-IP Advanced WAF and ASM XSS vulnerability CVE-2021-22993 Original Publication Date: 11 Mar, 2021 Security Advisory Description DOM-based XSS on DoS Profile properties page. (CVE-2021-22993) Impact An attacker can inject a malicious script into the BIG-IP Advanced WAF and ASM Configuration utility and trick users into executing malicious code. Security Advisory Status F5 Product Development has assigned ID 941449 (BIG-IP) 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. +-------------------+------+----------+----------+----------+------+----------+ | | |Versions |Fixes | |CVSSv3|Vulnerable| |Product |Branch|known to |introduced|Severity |score^|component | | | |be |in | |1 |or feature| | | |vulnerable| | | | | +-------------------+------+----------+----------+----------+------+----------+ | |16.x |16.0.0 - |16.0.1.1 | | | | | | |16.0.1 | | | | | | +------+----------+----------+ | | | | |15.x |15.1.0 - |15.1.2 | | | | | | |15.1.1 | | | | | | +------+----------+----------+ | | | | |14.x |14.1.0 - |14.1.3.1 | | |BIG-IP ASM| |BIG-IP (Advanced | |14.1.3 | | | |DoS | |WAF, ASM) +------+----------+----------+High |7.5 |Profile | | |13.x |13.1.0 - |13.1.3.6 | | |properties| | | |13.1.3 | | | |page | | +------+----------+----------+ | | | | |12.x |12.1.0 - |12.1.5.3 | | | | | | |12.1.5 | | | | | | +------+----------+----------+ | | | | |11.x |None |Not | | | | | | | |applicable| | | | +-------------------+------+----------+----------+----------+------+----------+ | |16.x |None |Not | | | | | | | |applicable| | | | | +------+----------+----------+ | | | | |15.x |None |Not | | | | | | | |applicable| | | | |BIG-IP (LTM, AAM, +------+----------+----------+ | | | |AFM, Analytics, |14.x |None |Not | | | | |APM, DDHD, DNS, | | |applicable|Not | | | |FPS, GTM, Link +------+----------+----------+vulnerable|None |None | |Controller, PEM, |13.x |None |Not | | | | |SSLO) | | |applicable| | | | | +------+----------+----------+ | | | | |12.x |None |Not | | | | | | | |applicable| | | | | +------+----------+----------+ | | | | |11.x |None |Not | | | | | | | |applicable| | | | +-------------------+------+----------+----------+----------+------+----------+ | |8.x |None |Not | | | | | | | |applicable| | | | | +------+----------+----------+ | | | |BIG-IQ Centralized |7.x |None |Not |Not |None |None | |Management | | |applicable|vulnerable| | | | +------+----------+----------+ | | | | |6.x |None |Not | | | | | | | |applicable| | | | +-------------------+------+----------+----------+----------+------+----------+ |Traffix SDC |5.x |None |Not |Not |None |None | | | | |applicable|vulnerable| | | +-------------------+------+----------+----------+----------+------+----------+ ^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. 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. Mitigation To mitigate this vulnerability, secure access to the BIG-IP Advanced WAF and ASM systems to ensure that the Configuration utility is accessible only by trusted users. To do so, refer to K13092: Overview of securing access to the BIG-IP system. Supplemental Information 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 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 - ---------------------------------------------------------------------------------- K06440657: BIG-IP ASM iControl REST vulnerability CVE-2021-23001 Original Publication Date: 11 Mar, 2021 Security Advisory Description The upload functionality in BIG-IP ASM allows an authenticated user to upload files to the BIG-IP system using a call to an undisclosed iControl REST endpoint. (CVE-2021-23001) Impact An unauthenticated malicious user can upload malicious files to use in future attacks, or simply upload large files to fill the BIG-IP system's disk space. Security Advisory Status F5 Product Development has assigned ID 935401 (BIG-IP) and 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. +-------------------+------+----------+----------+----------+------+----------+ | | |Versions |Fixes | |CVSSv3|Vulnerable| |Product |Branch|known to |introduced|Severity |score^|component | | | |be |in | |1 |or feature| | | |vulnerable| | | | | +-------------------+------+----------+----------+----------+------+----------+ | |16.x |16.0.0 - |16.0.1.1 | | | | | | |16.0.1 | | | | | | +------+----------+----------+ | | | | |15.x |15.0.0 - |15.1.2.1 | | | | | | |15.1.0 | | | | | | +------+----------+----------+ | | | | |14.x |14.1.0 - |14.1.4 | | |BIG-IP ASM| | | |14.1.2 | | | |file | |BIG-IP (ASM) +------+----------+----------+Medium |4.3 |transfer | | |13.x |13.1.0 - |13.1.3.6 | | |worker | | | |13.1.3 | | | | | | +------+----------+----------+ | | | | |12.x |12.1.0 - |12.1.5.3 | | | | | | |12.1.5 | | | | | | +------+----------+----------+ | | | | |11.x |11.6.1 - |11.6.5.3 | | | | | | |11.6.5 | | | | | +-------------------+------+----------+----------+----------+------+----------+ | |16.x |None |Not | | | | | | | |applicable| | | | | +------+----------+----------+ | | | | |15.x |None |Not | | | | | | | |applicable| | | | |BIG-IP (LTM, AAM, +------+----------+----------+ | | | |Advanced WAF, AFM, |14.x |None |Not | | | | |Analytics, APM, | | |applicable|Not | | | |DDHD, DNS, FPS, +------+----------+----------+vulnerable|None |None | |GTM, Link |13.x |None |Not | | | | |Controller, PEM, | | |applicable| | | | |SSLO) +------+----------+----------+ | | | | |12.x |None |Not | | | | | | | |applicable| | | | | +------+----------+----------+ | | | | |11.x |None |Not | | | | | | | |applicable| | | | +-------------------+------+----------+----------+----------+------+----------+ | |8.x |None |Not | | | | | | | |applicable| | | | | +------+----------+----------+ | | | |BIG-IQ Centralized |7.x |None |Not |Not |None |None | |Management | | |applicable|vulnerable| | | | +------+----------+----------+ | | | | |6.x |None |Not | | | | | | | |applicable| | | | +-------------------+------+----------+----------+----------+------+----------+ |Traffix SDC |5.x |None |Not |Not |None |None | | | | |applicable|vulnerable| | | +-------------------+------+----------+----------+----------+------+----------+ ^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. 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. Mitigation None Supplemental Information 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 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 iQIVAwUBYE7o1+NLKJtyKPYoAQhu/Q//eTIxpCaeyb+iPEX4GE93NodmplY8S/R2 1Ftag5Pe//xMxAnD8t+4qAeAQGZtR0gXDq1t2+l+rkQHHZdY6ev6XFLOEBF2B9QU wSzhmNFvky/nacdtYDKJ2z49m8HW0OyfakidrsCzhX+6eYPGgoGajJyLwt9tg5aX fdaHgM07e+5VfeCYBT7Clng5Oqy/z0oFHCfKQU6hj8vDGCZVBb2AAYDhUpRSIU6y 4bMktjNO3rrjXknftqvafYCAsdRkkCHV1uz82MlBz0q9MWzbtq3kJlpwCA3A7DmM Wm5gQcm+0LOWmnq+WAUzukmKajxAGwZFNyVGgNeZgbnUoK9nO4rSE6peNzKF+uZg sJCs3FQ8qRg69wDQDJBTbkQZKlhQdXpyh8CfB5QILpfKKpBBNjBzYFhQq5undFM7 uV3tmWezcpsxMrs+gql15Eam3exKIrgBb9amoJDyt8+TtxIVb5WGRc00J0c0YujR 1NxyXgjLZZu9DcEwyyfxYvKy3NisOTtAWj9ucBsIBf5L5wFwFe3QNjqopfj7ihow P4yRegAjhj1HLyClIOJhPwTwvI5t3de6fmBi3cXGYkuIaG8t6Uwop7lL9UIiHHbj N7SH/V+m8BsNgue66E22KT1UluKWyj3AYccy3zWvxJCGAEuCaTEhcBHvlOuaaaCp U29BqcYAB4U= =/1Wp -----END PGP SIGNATURE-----

Read More

The post ESB-2021.0872.2 – UPDATED ALERT [Appliance] BIG-IP Products: Multiple vulnerabilities appeared first on Malware Devil.



https://malwaredevil.com/2021/03/15/esb-2021-0872-2-updated-alert-appliance-big-ip-products-multiple-vulnerabilities/?utm_source=rss&utm_medium=rss&utm_campaign=esb-2021-0872-2-updated-alert-appliance-big-ip-products-multiple-vulnerabilities

ESB-2021.0903 – [Debian] pygments: Denial of service – Remote/unauthenticated

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

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

                               ESB-2021.0903
                         pygments security update
                               15 March 2021

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

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

Product:           pygments
Publisher:         Debian
Operating System:  Debian GNU/Linux
Impact/Access:     Denial of Service -- Remote/Unauthenticated
Resolution:        Patch/Upgrade
CVE Names:         CVE-2021-20270  

Reference:         ESB-2021.0890
                   ESB-2021.0849

Original Bulletin: 
   http://www.debian.org/security/2021/dsa-4870

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

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

- - -------------------------------------------------------------------------
Debian Security Advisory DSA-4870-1                   security@debian.org
https://www.debian.org/security/                       Moritz Muehlenhoff
March 12, 2021                        https://www.debian.org/security/faq
- - -------------------------------------------------------------------------

Package        : pygments
CVE ID         : CVE-2021-20270

It was discovered that Pygments, a syntax highlighting package written
in Python, could be forced into an infinite loop, resulting in denial
of service.

For the stable distribution (buster), this problem has been fixed in
version 2.3.1+dfsg-1+deb10u1.

We recommend that you upgrade your pygments packages.

For the detailed security status of pygments please refer to
its security tracker page at:
https://security-tracker.debian.org/tracker/pygments

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/

Mailing list: debian-security-announce@lists.debian.org
- -----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmBL3qAACgkQEMKTtsN8
TjYcsw//e/DuA3nNLvJQe7qHE+tlJpr462Fb5MXnwn5oOISdY9N4/5+i9OzB9g0i
dffRJRnXQnX8YMcB711fEmVwUQNuwsA3W2q3ezM5xfsKRl9RNOOlKlsbiiePOXlO
oc4mSFJAdpC+IUE92Q32Hr44Ep4iqcgfDlrJiLuNwlQ0C6Hy5wPD3KBSIs0GYAIl
yPxz07OyX/RHZmNAPbLpx2TK9eeWQeSvIo3EsdoGm0ky9MboahB159f/eoS5n2Uc
BvT1IuNbNjvmssTXl2PMAKOnFfrcPxNU+6EuAbwhVWj7kZTwHlYQ86GtmJVhvKzo
2ynZX0d2BQONIDX3z/2w8HdPPB2FsxbkHgjC3+1msfK8G4U6UMgvquLn/FDfAUiV
CFA2L8oAQBn4trh3s0/kmCsDV6C/EtmxnIuowUPoUwR+mFjrH8HNTxU3kyo9HfFh
eKNCXJX2NGWd2Q/PoMyVd5XPY4ZA/X5JjHFb8g8XPXXfG9rPnjvP2KYdHl1Hocmk
eazGCQRbU8yhTdJcopRDji5MghjqMseVbkuHO/jdABReqZc7zZstirX+MwLNHOaT
V9FhTvlYkGfckk8i7k5VuQ33jgY8CgWh5XphNhSITBCiSv2/nfgIOWIkUcvXtqVV
RhxziMHNtl7oE6yH//etXblyPpOXn40SWC6DnjBqtw1Rbly5EmM=
=3vzb
- -----END PGP SIGNATURE-----

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

iQIVAwUBYE7lWuNLKJtyKPYoAQikQw//afCZRkxlIZUhs6RkIXOaCXzJ442q5Ct+
rin/38enCFBZwYbhWysoqvJBCOA9DK0DHkY3EfLMBHg0r5i1fcTo8fOYmSbaH2o+
C3zmEPMbZFwgjXonmERG9ywJv6Pn69S5x7jAXpjgPoCBLwLqv0dA1cUqlCp8k1gi
E4iK3TaIkzfMHc98o4gKqixjXrt/qUoRplAyTagDS1qFO9/paM/jmDckrnwkTOo5
Q+2xZKpUg4jf4wIHdcmaEOgR3DiLfYHp0WFRHt7EP/4WXedVcuoCGcLVJdjvIimd
5uDWL0JgZtQDURnJr849kSsa6Rb/2Y+zx4p+BPUoQ72y9sficuRFFENsXUIowuCQ
nxW+r/zYxhyo9h6P+ta/hWe0R7/klgp3u04meqo4jdeQWG570HFu87eSJ5507v/E
M0S4Vgv+32vknX22UzeVwqu+o0WXl3yTOz7ci0VoznxhfH7a5ftqIZGOxjVTL37j
1/DakBO5/fhVQe3BpBZXoJdz8k2fQ/UFiCIXzAHHweqLmDWL3LthWehrqlRhpeWP
9ZBLG6oLIAconG7+R0KgZmo8eZrfgdAQ0/bZlvz0tRtmC5y98VHVJrIJn5mGxGvL
xUOTAE+BoqFDJAUWxkiEThKwSJ3fDE/P0iRLJgGLnflDEjhA1/fR/5zw0G5BHKlf
jRC+TFg9W/w=
=YYsK
-----END PGP SIGNATURE-----

Read More

The post ESB-2021.0903 – [Debian] pygments: Denial of service – Remote/unauthenticated appeared first on Malware Devil.



https://malwaredevil.com/2021/03/15/esb-2021-0903-debian-pygments-denial-of-service-remote-unauthenticated/?utm_source=rss&utm_medium=rss&utm_campaign=esb-2021-0903-debian-pygments-denial-of-service-remote-unauthenticated

ESB-2021.0902 – [SUSE] slurm_20_11 and pdsh: Multiple vulnerabilities

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

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

                               ESB-2021.0902
                 Security update for slurm_20_11 and pdsh
                               15 March 2021

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

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

Product:           slurm_20_11
                   pdsh
Publisher:         SUSE
Operating System:  SUSE
Impact/Access:     Execute Arbitrary Code/Commands -- Remote/Unauthenticated
                   Root Compromise                 -- Existing Account      
                   Modify Arbitrary Files          -- Remote/Unauthenticated
                   Denial of Service               -- Existing Account      
                   Access Confidential Data        -- Remote/Unauthenticated
                   Reduced Security                -- Remote/Unauthenticated
Resolution:        Patch/Upgrade
CVE Names:         CVE-2020-27746 CVE-2020-27745 CVE-2020-12693
                   CVE-2019-19728 CVE-2019-19727 CVE-2019-12838
                   CVE-2019-6438 CVE-2018-10995 CVE-2018-7033
                   CVE-2017-15566 CVE-2016-10030 

Reference:         ESB-2021.0322
                   ESB-2021.0202.2
                   ESB-2020.3134

Original Bulletin: 
   https://www.suse.com/support/update/announcement/2021/suse-su-20210773-1

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

SUSE Security Update: Security update for slurm_20_11 and pdsh

______________________________________________________________________________

Announcement ID:   SUSE-SU-2021:0773-1
Rating:            important
References:        #1018371 #1065697 #1085240 #1095508 #1123304 #1140709
                   #1155784 #1159692 #1172004 #1178890 #1178891
Cross-References:  CVE-2016-10030 CVE-2017-15566 CVE-2018-10995 CVE-2018-7033
                   CVE-2019-12838 CVE-2019-19727 CVE-2019-19728 CVE-2019-6438
                   CVE-2020-12693 CVE-2020-27745 CVE-2020-27746
Affected Products:
                   SUSE Linux Enterprise Module for HPC 12
______________________________________________________________________________

An update that fixes 11 vulnerabilities, contains one feature is now available.

Description:

This update for pdsh fixes the following issues:

  o Preparing pdsh for Slurm 20.11 (jsc#ECO-2412)
  o Simplify convoluted condition.


This update for slurm fixes the following issues:


  o Fix potential buffer overflows from use of unpackmem(). CVE-2020-27745 (bsc
    #1178890)
  o Fix potential leak of the magic cookie when sent as an argument to the
    xauth command. CVE-2020-27746 (bsc#1178891)
  o Add support for openPMIx also for Leap/SLE 15.0/1 (bsc#1173805).
  o Updated to 20.02.3 which fixes CVE-2020-12693 (bsc#1172004).
  o slurm-plugins will now also require pmix not only libpmix (bsc#1164326)
  o Removed autopatch as it doesn't work for the SLE-11-SP4 build.
  o Disable %arm builds as this is no longer supported.
  o pmix searches now also for libpmix.so.2 so that there is no dependency for
    devel package (bsc#1164386)
  o Update to version 20.02.0 (jsc#SLE-8491) * Fix minor memory leak in slurmd
    on reconfig. * Fix invalid ptr reference when rolling up data in the
    database. * Change shtml2html.py to require python3 for RHEL8 support, and
    match man2html.py. * slurm.spec - override "hardening" linker flags to
    ensure RHEL8 builds in a usable manner. * Fix type mismatches in the perl
    API. * Prevent use of uninitialized slurmctld_diag_stats. * Fixed various
    Coverity issues. * Only show warning about root-less topology in daemons. *
    Fix accounting of jobs in IGNORE_JOBS reservations. * Fix issue with batch
    steps state not loading correctly when upgrading from 19.05. * Deprecate
    max_depend_depth in SchedulerParameters and move it to
    DependencyParameters. * Silence erroneous error on slurmctld upgrade when
    loading federation state. * Break infinite loop in cons_tres dealing with
    incorrect tasks per tres request resulting in slurmctld hang. * Improve
    handling of --gpus-per-task to make sure appropriate number of GPUs is
    assigned to job. * Fix seg fault on cons_res when requesting --spread-job.


  o Move to python3 for everything but SLE-11-SP4 * For SLE-11-SP4 add a
    workaround to handle a python3 script (python2.7 compliant).


* sbatch - fix segfault when no newline at the end of a burst buffer file. *
Change scancel to only check job's base state when matching -t options. * Save
job dependency list in state files. * cons_tres - allow jobs to be run on
systems with root-less topologies. * Restore pre-20.02pre1 PrologSlurmctld
synchonization behavior to avoid various race conditions, and ensure proper
batch job launch. * Add new slurmrestd command/daemon which implements the
Slurm REST API.

  o standard slurm.conf uses now also SlurmctldHost on all build targets (bsc#
    1162377)


  o start slurmdbd after mariadb (bsc#1161716)


  o Update to version 19.05.5 (jsc#SLE-8491) * Includes security fixes
    CVE-2019-19727, CVE-2019-19728, CVE-2019-12838. * Disable i586 builds as
    this is no longer supported. * Create libnss_slurm package to support user
    and group resolution thru slurmstepd.


  o Update to v18.08.9 for fixing CVE-2019-19728 (bsc#1159692). * Make Slurm
    compile on linux after sys/sysctl.h was deprecated. * Install
    slurmdbd.conf.example with 0600 permissions to encourage secure use.
    CVE-2019-19727. * srun - do not continue with job launch if --uid fails.
    CVE-2019-19728.


  o added pmix support jsc#SLE-10800


  o Use --with-shared-libslurm to build slurm binaries using libslurm.
  o Make libslurm depend on slurm-config.


  o Fix ownership of /var/spool/slurm on new installations and upgrade (bsc#
    1158696).


  o Fix permissions of slurmdbd.conf (bsc#1155784, CVE-2019-19727).
  o Fix %posttrans macro _res_update to cope with added newline (bsc#1153259).


  o Add package slurm-webdoc which sets up a web server to provide the
    documentation for the version shipped.


  o Move srun from 'slurm' to 'slurm-node': srun is required on the nodes as
    well so sbatch will work. 'slurm-node' is a requirement when 'slurm' is
    installed (bsc#1153095).


  o Updated to 18.08.8 for fixing (CVE-2019-12838, bsc#1140709, jsc#SLE-7341,
    jsc#SLE-7342) * Update "xauth list" to use the same 10000ms timeout as the
    other xauth commands. * Fix issue in gres code to handle a gres cnt of 0. *
    Don't purge jobs if backfill is running. * Verify job is pending add/
    removing accrual time. * Don't abort when the job doesn't have an
    association that was removed before the job was able to make it to the
    database. * Set state_reason if select_nodes() fails job for QOS or
    Account. * Avoid seg_fault on referencing association without a valid_qos
    bitmap. * If Association/QOS is removed on a pending job set that job as
    ineligible. * When changing a jobs account/qos always make sure you remove
    the old limits. * Don't reset a FAIL_QOS or FAIL_ACCOUNT job reason until
    the qos or account changed. * Restore "sreport -T ALL" functionality. *
    Correctly typecast signals being sent through the api. * Properly
    initialize structures throughout Slurm. * Sync "numtask" squeue format
    option for jobs and steps to "numtasks". * Fix sacct -PD to avoid CA before
    start jobs. * Fix potential deadlock with backup slurmctld. * Fixed issue
    with jobs not appearing in sacct after dependency satisfied. * Fix showing
    non-eligible jobs when asking with -j and not -s. * Fix issue with backfill
    scheduler scheduling tasks of an array when not the head job. *
    accounting_storage/mysql - fix SIGABRT in the archive load logic. *
    accounting_storage/mysql - fix memory leak in the archive load logic. *
    Limit records per single SQL statement when loading archived data. * Fix
    unnecessary reloading of job submit plugins. * Allow job submit plugins to
    be turned on/off with a reconfigure. * Fix segfault when loading/unloading
    Lua job submit plugin multiple times. * Fix printing duplicate error
    messages of jobs rejected by job submit plugin. * Fix printing of job
    submit plugin messages of het jobs without pack id. * Fix memory leak in
    group_cache.c * Fix jobs stuck from FedJobLock when requeueing in a
    federation * Fix requeueing job in a federation of clusters with differing
    associations * sacctmgr - free memory before exiting in 'sacctmgr show
    runaway'. * Fix seff showing memory overflow when steps tres mem usage is
    0. * Upon archive file name collision, create new archive file instead of
    overwriting the old one to prevent lost records. * Limit archive files to
    50000 records per file so that archiving large databases will succeed. *
    Remove stray newlines in SPANK plugin error messages. * Fix archive loading
    events. * In select/cons_res: Only allocate 1 CPU per node with the
    --overcommit and --nodelist options. * Fix main scheduler from potentially
    not running through whole queue. * cons_res/job_test - prevent a job from
    overallocating a node memory. * cons_res/job_test - fix to consider a
    node's current allocated memory when testing a job's memory request. * Fix
    issue where multi-node job steps on cloud nodes wouldn't finish cleaning up
    until the end of the job (rather than the end of the step). * Fix issue
    with a 17.11 sbcast call to a 18.08 daemon. * Add new job bit_flags of
    JOB_DEPENDENT. * Make it so dependent jobs reset the AccrueTime and do not
    count against any AccrueTime limits. * Fix sacctmgr --parsable2 output for
    reservations and tres. * Prevent slurmctld from potential segfault after
    job_start_data() called for completing job. * Fix jobs getting on nodes
    with "scontrol reboot asap". * Record node reboot events to database. * Fix
    node reboot failure message getting to event table. * Don't write "(null)"
    to event table when no event reason exists. * Fix minor memory leak when
    clearing runaway jobs. * Avoid flooding slurmctld and logging when prolog
    complete RPC errors occur. * Fix GCC 9 compiler warnings. * Fix seff human
    readable memory string for values below a megabyte. * Fix dump/load of
    rejected heterogeneous jobs. * For heterogeneous jobs, do not count the
    each component against the QOS or association job limit multiple times. *
    slurmdbd - avoid reservation flag column corruption with the use of newer
    flags, instead preserve the older flag fields that we can still fit in the
    smallint field, and discard the rest. * Fix security issue in
    accounting_storage/mysql plugin on archive file loads by always escaping
    strings within the slurmdbd. CVE-2019-12838. * Fix underflow causing decay
    thread to exit. * Fix main scheduler not considering hetjobs when building
    the job queue. * Fix regression for sacct to display old jobs without a
    start time. * Fix setting correct number of gres topology bits. * Update
    hetjobs pending state reason when appropriate. * Fix accounting_storage/
    filetxt's understanding of TRES. * Set Accrue time when not enforcing
    limits. * Fix srun segfault when requesting a hetjob with test_exec or
    bcast options. * Hide multipart priorities log message behind Priority
    debug flag. * sched/backfill - Make hetjobs sensitive to bf_max_job_start.
    * Fix slurmctld segfault due to job's partition pointer NULL dereference. *
    Fix issue with OR'ed job dependencies. * Add new job's bit_flags of
    INVALID_DEPEND to prevent rebuilding a job's dependency string when it has
    at least one invalid and purged dependency. * Promote federation unsynced
    siblings log message from debug to info. * burst_buffer/cray - fix
    slurmctld SIGABRT due to illegal read/writes. * burst_buffer/cray - fix
    memory leak due to unfreed job script content. * node_features/knl_cray -
    fix script_argv use-after-free. * burst_buffer/cray - fix script_argv
    use-after-free. * Fix invalid reads of size 1 due to non null-terminated
    string reads. * Add extra debug2 logs to identify why BadConstraints reason
    is set.


  o Do not build hdf5 support where not available.


  o Add support for version updates on SLE: Update packages to a later version
    than the version supported originally on SLE will receive a version string
    in their package name.


  o added the hdf5 job data gathering plugin


  o Add backward compatibility with SLE-11 SP4


  o Update to version 18.08.05: * Add mitigation for a potential heap overflow
    on 32-bit systems in xmalloc. (CVE-2019-6438, bsc#1123304)
  o Fix fallout from 750cc23ed for CVE-2019-6438.


  o Update to 18.08.04, with following highlights * Fix message sent to user to
    display preempted instead of time limit when a job is preempted. * Fix
    memory leak when a failure happens processing a nodes gres config. *
    Improve error message when failures happen processing a nodes gres config.
    * Don't skip jobs in scontrol hold. * Allow --cpu-bind=verbose to be used
    with SLURM_HINT environment variable. * Enhanced handling for runaway jobs
    * cons_res: Delay exiting cr_job_test until after cores/cpus are calculated
    and distributed. * Don't check existence of srun --prolog or --epilog
    executables when set to "none" and SLURM_TEST_EXEC is used. * Add "P"
    suffix support to job and step tres specifications. * Fix jobacct_gather/
    cgroup to work correctly when more than one task is started on a node. *
    salloc - set SLURM_NTASKS_PER_CORE and SLURM_NTASKS_PER_SOCKET in the
    environment if the corresponding command line options are used. * slurmd -
    fix handling of the -f flag to specify alternate config file locations. *
    Add SchedulerParameters option of bf_ignore_newly_avail_nodes to avoid
    scheduling lower priority jobs on resources that become available during
    the backfill scheduling cycle when bf_continue is enabled. * job_submit/
    lua: Add several slurmctld return codes and add user/group info * salloc/
    sbatch/srun - print warning if mutually exclusive options of --mem and
    --mem-per-cpu are both set.


  o restarting services on update only when activated
  o added rotation of logs
  o Added backported patches which harden the pam module pam_slurm_adopt. (BOO#
    1116758)


  o Moved config man pages to a separate package: This way, they won't get
    installed on compute nodes.


  o added correct link flags for perl bindings (bsc#1108671) * perl:Switch is
    required by slurm torque wrappers


  o Fix Requires(pre) and Requires(post) for slurm-config and slurm-node. This
    fixes issues with failing slurm user creation when installed during initial
    system installation. (bsc#1109373)


  o When using a remote shared StateSaveLocation, slurmctld needs to be started
    after remote filesystems have become available. Add 'remote-fs.target' to
    the 'After=' directive in slurmctld.service (bsc#1103561).


  o Update to 17.11.8 * Fix incomplete RESPONSE_[RESOURCE|JOB_PACK]_ALLOCATION
    building path. * Do not allocate nodes that were marked down due to the
    node not responding by ResumeTimeout. * task/cray plugin - search for
    "mems" cgroup information in the file "cpuset.mems" then fall back to the
    file "mems". * Fix ipmi profile debug uninitialized variable. * PMIx: fixed
    the direct connect inline msg sending. * MYSQL: Fix issue not handling all
    fields when loading an archive dump. * Allow a job_submit plugin to change
    the admin_comment field during job_submit_plugin_modify(). * job_submit/lua
    - fix access into reservation table. * MySQL - Prevent deadlock caused by
    archive logic locking reads. * Don't enforce MaxQueryTimeRange when
    requesting specific jobs. * Modify --test-only logic to properly support
    jobs submitted to more than one partition. * Prevent slurmctld from abort
    when attempting to set non-existing qos as def_qos_id. * Add new job
    dependency type of "afterburstbuffer". The pending job will be delayed
    until the first job completes execution and it's burst buffer stage-out is
    completed. * Reorder proctrack/task plugin load in the slurmstepd to match
    that of slurmd and avoid race condition calling task before proctrack can
    introduce. * Prevent reboot of a busy KNL node when requesting inactive
    features. * Revert to previous behavior when requesting memory per cpu/node
    introduced in 17.11.7. * Fix to reinitialize previously adjusted job
    members to their original value when validating the job memory in
    multi-partition requests. * Fix _step_signal() from always returning
    SLURM_SUCCESS. * Combine active and available node feature change logs on
    one line rather than one line per node for performance reasons. * Prevent
    occasionally leaking freezer cgroups. * Fix potential segfault when closing
    the mpi/pmi2 plugin. * Fix issues with --exclusive=[user|mcs] to work
    correctly with preemption or when job requests a specific list of hosts. *
    Make code compile with hdf5 1.10.2+ * mpi/pmix: Fixed the collectives
    canceling. * SlurmDBD: improve error message handling on archive load
    failure. * Fix incorrect locking when deleting reservations. * Fix
    incorrect locking when setting up the power save module. * Fix setting
    format output length for squeue when showing array jobs. * Add xstrstr
    function. * Fix printing out of --hint options in sbatch, salloc --help. *
    Prevent possible divide by zero in _validate_time_limit(). * Add Delegate=
    yes to the slurmd.service file to prevent systemd from interfering with the
    jobs' cgroup hierarchies. * Change the backlog argument to the listen()
    syscall within srun to 4096 to match elsewhere in the code, and avoid
    communication problems at scale.


Fix race in the slurmctld backup controller which prevents it to clean up
allocations on nodes properly after failing over (bsc#1084917).

  o Handled %license in a backward compatible manner.


  o Add a 'Recommends: slurm-munge' to slurm-slurmdbd.


  o Shield comments between script snippets with a %{!nil:...} to avoid them
    being interpreted as scripts - in which case the update level is passed as
    argument (see chapter 'Shared libraries' in:
    https://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets) (bsc#
    1100850).


  o Update from 17.11.5 to 17.11.7
  o Fix security issue in handling of username and gid fields CVE-2018-10995
    and bsc#1095508 what implied an update from 17.11.5 to 17.11.7 Highlights
    of 17.11.6:
    * CRAY - Add slurmsmwd to the contribs/cray dir * PMIX - Added the direct
    connect authentication. * Prevent the backup slurmctld from losing the
    active/available node features list on takeover. * Be able to force
    power_down of cloud node even if in power_save state. * Allow cloud nodes
    to be recognized in Slurm when booted out of band. * Numerous fixes - check
    'NEWS' file. Highlights of 17.11.7:
    * Notify srun and ctld when unkillable stepd exits. * Numerous fixes -
    check 'NEWS' file. * Fixes daemoniziation in newly introduced slurmsmwd
    daemon.
  o Rename: * remain in sync with commit messages which introduced that file


  o Avoid running pretrans scripts when running in an instsys: there may be not
    much installed, yet. pretrans code should be done in lua, this way, it will
    be executed by the rpm-internal lua interpreter and not be passed to a
    shell which may not be around at the time this scriptlet is run (bsc#
    1090292).


  o Add requires for slurm-sql to the slurmdbd package.


  o Package READMEs for pam and pam_slurm_adopt.
  o Use the new %%license directive for COPYING file. Fix interaction with
    systemd: systemd expects that a daemonizing process doesn't go away until
    the PID file with it PID of the daemon has bee written (bsc#1084125).


  o Make sure systemd services get restarted only when all packages are in a
    consistent state, not in the middle of an 'update' transaction (bsc#
    1088693). Since the %postun scripts that run on update are from the old
    package they cannot be changed - thus we work around the restart breakage.


  o fixed wrong log file location in slurmdbd.conf and fixed pid location for
    slurmdbd and made slurm-slurmdbd depend on slurm config which provides the
    dir /var/run/slurm (bsc#1086859).


  o added comment for (bsc#1085606)


  o Fix security issue in accounting_storage/mysql plugin by always escaping
    strings within the slurmdbd. CVE-2018-7033 (bsc#1085240).
  o Update slurm to v17.11.5 (FATE#325451) Highlights of 17.11: * Support for
    federated clusters to manage a single work-flow across a set of clusters. *
    Support for heterogeneous job allocations (various processor types, memory
    sizes, etc. by job component). Support for heterogeneous job steps within a
    single MPI_COMM_WORLD is not yet supported for most configurations. * X11
    support is now fully integrated with the main Slurm code. Remove any X11
    plugin configured in your plugstack.conf file to avoid errors being logged
    about conflicting options. * Added new advanced reservation flag of "flex",
    which permits jobs requesting the reservation to begin prior to the
    reservation's start time and use resources inside or outside of the
    reservation. A typical use case is to prevent jobs not explicitly
    requesting the reservation from using those reserved resources rather than
    forcing jobs requesting the reservation to use those resources in the time
    frame reserved. * The sprio command has been modified to report a job's
    priority information for every partition the job has been submitted to. *
    Group ID lookup performed at job submit time to avoid lookup on all compute
    nodes. Enable with PrologFlags=SendGIDs configuration parameter. * Slurm
    commands and daemons dynamically link to libslurmfull.so instead of
    statically linking. This dramatically reduces the footprint of Slurm. * In
    switch plugin, added plugin_id symbol to plugins and wrapped
    switch_jobinfo_t with dynamic_plugin_data_t in interface calls in order to
    pass switch information between clusters with different switch types. *
    Changed default ProctrackType to cgroup. * Changed default
    sched_min_interval from 0 to 2 microseconds. * Added new 'scontrol write
    batch_script ' command to fetch a job's batch script. Removed the ability
    to see the script as part of the 'scontrol -dd show job' command. * Add new
    "billing" TRES which allows jobs to be limited based on the job's billable
    TRES calculated by the job's partition's TRESBillingWeights. * Regular user
    use of "scontrol top" command is now disabled. Use the configuration
    parameter "SchedulerParameters=enable_user_top" to enable that
    functionality. The configuration parameter "SchedulerParameters=
    disable_user_top" will be silently ignored. * Change default to let pending
    jobs run outside of reservation after reservation is gone to put jobs in
    held state. Added NO_HOLD_JOBS_AFTER_END reservation flag to use old
    default. Support for PMIx v2.0 as well as UCX support. * Remove plugins for
    obsolete MPI stacks:
    - lam - mpich1_p4 - mpich1_shmem - mvapich * Numerous fixes - check 'NEWS'
    file. Replaced by sed script.
  o Fix some rpmlint warnings.


  o moved config files to slurm-config package (FATE#324574).


  o Moved slurmstepd and man page into slurm-node due to slurmd dependency
  o Moved config files into slurm-node
  o Moved slurmd rc scripts into slurm-node
  o Made slurm-munge require slurm-plugins instead of slurm itself - slurm-node
    suggested slurm-munge, causing the whole slurm to be installed. The
    slurm-plugins seems to be a more base class (FATE#324574).


  o split up light wight slurm-node package for deployment on nodes (FATE#
    324574).


  o Package so-versioned libs separately. libslurm is expected to change more
    frequently and thus is packaged separately from libpmi.


  o Updated to 17.02.9 to fix CVE-2017-15566 (bsc#1065697). Changes in 17.0.9 *
    When resuming powered down nodes, mark DOWN nodes right after ResumeTimeout
    has been reached (previous logic would wait about one minute longer). * Fix
    sreport not showing full column name for TRES Count. * Fix
    slurmdb_reservations_get() giving wrong usage data when job's spanned
    reservation that was modified. * Fix sreport reservation utilization report
    showing bad data. * Show all TRES' on a reservation in sreport reservation
    utilization report by default. * Fix sacctmgr show reservation handling
    "end" parameter. * Work around issue with sysmacros.h and gcc7 / glibc
    2.25. * Fix layouts code to only allow setting a boolean. * Fix sbatch
    --wait to keep waiting even if a message timeout occurs. * CRAY - If
    configured with NodeFeatures=knl_cray and there are non-KNL nodes which
    include no features the slurmctld will abort without this patch when
    attemping strtok_r(NULL). * Fix regression in 17.02.7 which would run the
    spank_task_privileged as part of the slurmstepd instead of it's child
    process. * Fix security issue in Prolog and Epilog by always prepending
    SPANK_ to all user-set environment variables. CVE-2017-15566. Changes in
    17.0.8:
    * Add 'slurmdbd:' to the accounting plugin to notify message is from dbd
    instead of local. * mpi/mvapich - Buffer being only partially cleared. No
    failures observed. * Fix for job --switch option on dragonfly network. * In
    salloc with --uid option, drop supplementary groups before changing UID. *
    jobcomp/elasticsearch - strip any trailing slashes from JobCompLoc. *
    jobcomp/elasticsearch - fix memory leak when transferring generated buffer.
    * Prevent slurmstepd ABRT when parsing gres.conf CPUs. * Fix sbatch
    --signal to signal all MPI ranks in a step instead of just those on node 0.
    * Check multiple partition limits when scheduling a job that were
    previously only checked on submit. * Cray: Avoid running application/step
    Node Health Check on the external job step. * Optimization enhancements for
    partition based job preemption. * Address some build warnings from GCC 7.1,
    and one possible memory leak if /proc is inaccessible. * If creating/
    altering a core based reservation with scontrol/sview on a remote cluster
    correctly determine the select type. * Fix autoconf test for libcurl when
    clang is used. * Fix default location for cgroup_allowed_devices_file.conf
    to use correct default path. * Document NewName option to sacctmgr. *
    Reject a second PMI2_Init call within a single step to prevent slurmstepd
    from hanging. * Handle old 32bit values stored in the database for
    requested memory correctly in sacct. * Fix memory leaks in the task/cgroup
    plugin when constraining devices. * Make extremely verbose info messages
    debug2 messages in the task/cgroup plugin when constraining devices. * Fix
    issue that would deny the stepd access to /dev/null where GRES has a 'type'
    but no file defined. * Fix issue where the slurmstepd would fatal on job
    launch if you have no gres listed in your slurm.conf but some in gres.conf.
    * Fix validating time spec to correctly validate various time formats. *
    Make scontrol work correctly with job update timelimit [+|-]=. * Reduce the
    visibily of a number of warnings in _part_access_check. * Prevent segfault
    in sacctmgr if no association name is specified for an update command. *
    burst_buffer/cray plugin modified to work with changes in Cray UP05
    software release. * Fix job reasons for jobs that are violating assoc
    MaxTRESPerNode limits. * Fix segfault when unpacking a 16.05 slurm_cred in
    a 17.02 daemon. * Fix setting TRES limits with case insensitive TRES names.
    * Add alias for xstrncmp() -- slurm_xstrncmp(). * Fix sorting of case
    insensitive strings when using xstrcasecmp(). * Gracefully handle race
    condition when reading /proc as process exits. * Avoid error on Cray
    duplicate setup of core specialization. * Skip over undefined (hidden in
    Slurm) nodes in pbsnodes. * Add empty hashes in perl api's slurm_load_node
    () for hidden nodes. * CRAY - Add rpath logic to work for the alpscomm
    libs. * Fixes for administrator extended TimeLimit (job reason & time limit
    reset). * Fix gres selection on systems running select/linear. * sview:
    Added window decorator for maximize,minimize,close buttons for all systems.
    * squeue: interpret negative length format specifiers as a request to
    delimit values with spaces. * Fix the torque pbsnodes wrapper script to
    parse a gres field with a type set correctly.
  o Fixed ABI version of libslurm.


  o Trim redundant wording in descriptions.


  o Updated to slurm 17-02-7-1 * Added python as BuildRequires * Removed
    sched-wiki package * Removed slurmdb-direct package * Obsoleted sched-wiki
    and slurmdb-direct packages * Removing Cray-specific files * Added /etc/
    slurm/layout.d files (new for this version) * Remove /etc/slurm/cgroup
    files from package * Added lib/slurm/mcs_account.so * Removed lib/slurm/
    jobacct_gather_aix.so * Removed lib/slurm/job_submit_cnode.so
  o Created slurm-sql package
  o Moved files from slurm-plugins to slurm-torque package
  o Moved creation of /usr/lib/tmpfiles.d/slurm.conf into slurm.spec * Removed
    tmpfiles.d-slurm.conf
  o Changed /var/run path for slurm daemons to /var/run/slurm (FATE#324026).


  o Made tmpfiles_create post-install macro SLE12 SP2 or greater
  o Directly calling systemd-tmpfiles --create for before SLE12 SP2


  o Allows OpenSUSE Factory build as well
  o Removes unused .service files from project
  o Adds /var/run/slurm to /usr/lib/tmpfiles.d for boottime creation * Patches
    upstream .service files to allow for /var/run/slurm path * Modifies
    slurm.conf to allow for /var/run/slurm path


  o Move wrapper script mpiexec provided by slrum-torque to mpiexec.slurm to
    avoid conflicts. This file is normally provided by the MPI implementation
    (bsc#1041706).


  o Replace remaining ${RPM_BUILD_ROOT}s.
  o Improve description.
  o Fix up changelog.


  o Spec file: Replace "Requires : slurm-perlapi" by "Requires: perl-slurm = %
    {version}" (bsc#1031872).


  o Trim redundant parts of description. Fixup RPM groups.
  o Replace unnecessary %__ macro indirections; replace historic $RPM_*
    variables by macros.


  o Use %slurm_u and %slurm_g macros defined at the beginning of the spec file
    when adding the slurm user/group for consistency.
  o Define these macros to daemon,root for non-systemd.
  o For anything newer than Leap 42.1 or SLE-12-SP1 build OpenHPC compatible.


  o Updated to 16.05.8.1 * Remove StoragePass from being printed out in the
    slurmdbd log at debug2 level. * Defer PATH search for task program until
    launch in slurmstepd. * Modify regression test1.89 to avoid leaving
    vestigial job. Also reduce logging to reduce likelyhood of Expect buffer
    overflow. * Do not PATH search for mult-prog launches if LaunchParamters=
    test_exec is enabled. * Fix for possible infinite loop in select/cons_res
    plugin when trying to satisfy a job's ntasks_per_core or socket
    specification. * If job is held for bad constraints make it so once updated
    the job doesn't go into JobAdminHeld. * sched/backfill - Fix logic to
    reserve resources for jobs that require a node reboot (i.e. to change KNL
    mode) in order to start. * When unpacking a node or front_end record from
    state and the protocol version is lower than the min version, set it to the
    min. * Remove redundant lookup for part_ptr when updating a reservation's
    nodes. * Fix memory and file descriptor leaks in slurmd daemon's sbcast
    logic. * Do not allocate specialized cores to jobs using the --exclusive
    option. * Cancel interactive job if Prolog failure with "PrologFlags=
    contain" or "PrologFlags=alloc" configured. Send new error prolog failure
    message to the salloc or srun command as needed. * Prevent possible
    out-of-bounds read in slurmstepd on an invalid #! line. * Fix check for
    PluginDir within slurmctld to work with multiple directories. * Cancel
    interactive jobs automatically on communication error to launching srun/
    salloc process. * Fix security issue caused by insecure file path handling
    triggered by the failure of a Prolog script. To exploit this a user needs
    to anticipate or cause the Prolog to fail for their job. CVE-2016-10030
    (bsc#1018371).
  o Replace group/user add macros with function calls.
  o Fix array initialzation and ensure strings are always NULL terminated in
  o pam_slurm.c (bsc#1007053).
  o Disable building with netloc support: the netloc API is part of the devel
    branch of hwloc. Since this devel branch was included accidentally and has
    been reversed since, we need to disable this for the time being.
  o Conditionalized architecture specific pieces to support non-x86
    architectures better.


  o Remove: unneeded 'BuildRequires: python'
  o Add: BuildRequires: freeipmi-devel BuildRequires: libibmad-devel
    BuildRequires: libibumad-devel so they are picked up by the slurm build.
  o Enable modifications from openHPC Project.
  o Enable lua API package build.
  o Add a recommends for slurm-munge to the slurm package: This is way, the
    munge auth method is available and slurm works out of the box.
  o Create /var/lib/slurm as StateSaveLocation directory. /tmp is dangerous.


  o Create slurm user/group in preinstall script.


  o Keep %{_libdir}/libpmi* and %{_libdir}/mpi_pmi2* on SUSE.


  o Fix build with and without OHCP_BUILD define.
  o Fix build for systemd and non-systemd.


  o Updated to 16-05-5 - equvalent to OpenHPC 1.2. * Fix issue with resizing
    jobs and limits not be kept track of correctly. * BGQ - Remove
    redeclaration of job_read_lock. * BGQ - Tighter locks around structures
    when nodes/cables change state. * Make it possible to change CPUsPerTask
    with scontrol. * Make it so scontrol update part qos= will take away a
    partition QOS from a partition. * Backfill scheduling properly synchronized
    with Cray Node Health Check. Prior logic could result in highest priority
    job getting improperly postponed. * Make it so daemons also support
    TopologyParam=NoInAddrAny. * If scancel is operating on large number of
    jobs and RPC responses from slurmctld daemon are slow then introduce a
    delay in sending the cancel job requests from scancel in order to reduce
    load on slurmctld. * Remove redundant logic when updating a job's task
    count. * MySQL - Fix querying jobs with reservations when the id's have
    rolled. * Perl - Fix use of uninitialized variable in
    slurm_job_step_get_pids. * Launch batch job requsting --reboot after the
    boot completes. * Do not attempt to power down a node which has never
    responded if the slurmctld daemon restarts without state. * Fix for
    possible slurmstepd segfault on invalid user ID. * MySQL - Fix for possible
    race condition when archiving multiple clusters at the same time. * Add
    logic so that slurmstepd can be launched under valgrind. * Increase buffer
    size to read /proc/*/stat files. * Remove the SchedulerParameters option of
    "assoc_limit_continue", making it the default value. Add option of
    "assoc_limit_stop". If "assoc_limit_stop" is set and a job cannot start due
    to association limits, then do not attempt to initiate any lower priority
    jobs in that partition. Setting this can decrease system throughput and
    utlization, but avoid potentially starving larger jobs by preventing them
    from launching indefinitely. * Update a node's socket and cores per socket
    counts as needed after a node boot to reflect configuration changes which
    can occur on KNL processors. Note that the node's total core count must not
    change, only the distribution of cores across varying socket counts (KNL
    NUMA nodes treated as sockets by Slurm). * Rename partition configuration
    from "Shared" to "OverSubscribe". Rename salloc, sbatch, srun option from
    "--shared" to "--oversubscribe". The old options will continue to function.
    Output field names also changed in scontrol, sinfo, squeue and sview. * Add
    SLURM_UMASK environment variable to user job. * knl_conf: Added new
    configuration parameter of CapmcPollFreq. * Cleanup two minor Coverity
    warnings. * Make it so the tres units in a job's formatted string are
    converted like they are in a step. * Correct partition's MaxCPUsPerNode
    enforcement when nodes are shared by multiple partitions. * node_feature/
    knl_cray - Prevent slurmctld GRES errors for "hbm" references. * Display
    thread name instead of thread id and remove process name in stderr logging
    for "thread_id" LogTimeFormat. * Log IP address of bad incomming message to
    slurmctld. * If a user requests tasks, nodes and ntasks-per-node and
    tasks-per-node/nodes != tasks print warning and ignore ntasks-per-node. *
    Release CPU "owner" file locks. * Update seff to fix warnings with ncpus,
    and list slurm-perlapi dependency in spec file. * Allow QOS timelimit to
    override partition timelimit when EnforcePartLimits is set to all/any. *
    Make it so qsub will do a "basename" on a wrapped command for the output
    and error files. * Add logic so that slurmstepd can be launched under
    valgrind. * Increase buffer size to read /proc/*/stat files. * Prevent job
    stuck in configuring state if slurmctld daemon restarted while
    PrologSlurmctld is running. Also re-issue burst_buffer/pre-load operation
    as needed. * Move test for job wait reason value of BurstBufferResources
    and BurstBufferStageIn later in the scheduling logic. * Document which srun
    options apply to only job, only step, or job and step allocations. * Use
    more compatible function to get thread name (>= 2.6.11). * Make it so the
    extern step uses a reverse tree when cleaning up. * If extern step doesn't
    get added into the proctrack plugin make sure the sleep is killed. * Add
    web links to Slurm Diamond Collectors (from Harvard University) and
    collectd (from EDF). * Add job_submit plugin for the "reboot" field. * Make
    some more Slurm constants (INFINITE, NO_VAL64, etc.) available to
    job_submit/lua plugins. * Send in a -1 for a taskid into
    spank_task_post_fork for the extern_step. * MYSQL - Sightly better logic if
    a job completion comes in with an end time of 0. * task/cgroup plugin is
    configured with ConstrainRAMSpace=yes, then set soft memory limit to
    allocated memory limit (previously no soft limit was set). * Streamline
    when schedule() is called when running with message aggregation on batch
    script completes. * Fix incorrect casting when [un]packing derived_ec on
    slurmdb_job_rec_t. * Document that persistent burst buffers can not be
    created or destroyed using the salloc or srun --bb options. * Add support
    for setting the SLURM_JOB_ACCOUNT, SLURM_JOB_QOS and SLURM_JOB_RESERVAION
    environment variables are set for the salloc command. Document the same
    environment variables for the salloc, sbatch and srun commands in their man
    pages. * Fix issue where sacctmgr load cluster.cfg wouldn't load
    associations that had a partition in them. * Don't return the extern step
    from sstat by default. * In sstat print 'extern' instead of 4294967295 for
    the extern step. * Make advanced reservations work properly with core
    specialization. * slurmstepd modified to pre-load all relevant plugins at
    startup to avoid the possibility of modified plugins later resulting in
    inconsistent API or data structures and a failure of slurmstepd. * Export
    functions from parse_time.c in libslurm.so. * Export unit convert functions
    from slurm_protocol_api.c in libslurm.so. * Fix scancel to allow multiple
    steps from a job to be cancelled at once. * Update and expand upgrade guide
    (in Quick Start Administrator web page). * burst_buffer/cray: Requeue, but
    do not hold a job which fails the pre_run operation. * Insure reported
    expected job start time is not in the past for pending jobs. * Add support
    for PMIx v2. Required for FATE#316379.


  o Setting 'download_files' service to mode='localonly' and adding source
    tarball. (Required for Factory).


  o version 15.08.7.1 * Remove the 1024-character limit on lines in batch
    scripts. task/affinity: Disable core-level task binding if more CPUs
    required than available cores. * Preemption/gang scheduling: If a job is
    suspended at slurmctld restart or reconfiguration time, then leave it
    suspended rather than resume+suspend. * Don't use lower weight nodes for
    job allocation when topology/tree used. * Don't allow user specified
    reservation names to disrupt the normal reservation sequeuece numbering
    scheme. * Avoid hard-link/copy of script/environment files for job arrays.
    Use the master job record file for all tasks of the job array. NOTE: Job
    arrays submitted to Slurm version 15.08.6 or later will fail if the
    slurmctld daemon is downgraded to an earlier version of Slurm. * In
    slurmctld log file, log duplicate job ID found by slurmd. Previously was
    being logged as prolog/epilog failure. * If a job is requeued while in the
    process of being launch, remove it's job ID from slurmd's record of active
    jobs in order to avoid generating a duplicate job ID error when launched
    for the second time (which would drain the node). * Cleanup messages when
    handling job script and environment variables in older directory structure
    formats. * Prevent triggering gang scheduling within a partition if
    configured with PreemptType=partition_prio and PreemptMode=suspend,gang. *
    Decrease parallelism in job cancel request to prevent denial of service
    when cancelling huge numbers of jobs. * If all ephemeral ports are in use,
    try using other port numbers. * Prevent "scontrol update job" from updating
    jobs that have already finished. * Show requested TRES in "squeue -O tres"
    when job is pending. * Backfill scheduler: Test association and QOS node
    limits before reserving resources for pending job. * Many bug fixes.
  o Use source services to download package.
  o Fix code for new API of hwloc-2.0.
  o package netloc_to_topology where avialable.
  o Package documentation.


  o version 15.08.3 * Many new features and bug fixes. See NEWS file
  o update files list accordingly
  o fix wrong end of line in some files


  o version 14.11.8 * Many bug fixes. See NEWS file
  o update files list accordingly


  o add missing systemd requirements
  o add missing rclink


  o version 14.03.9 * Many bug fixes. See NEWS file
  o add systemd support


  o version 14.03.6 * Added support for native Slurm operation on Cray systems
    (without ALPS). * Added partition configuration parameters AllowAccounts,
    AllowQOS, DenyAccounts and DenyQOS to provide greater control over use. *
    Added the ability to perform load based scheduling. Allocating resources to
    jobs on the nodes with the largest number if idle CPUs. * Added support for
    reserving cores on a compute node for system services (core specialization)
    * Add mechanism for job_submit plugin to generate error message for srun,
    salloc or sbatch to stderr. * Support for Postgres database has long since
    been out of date and problematic, so it has been removed entirely. If you
    would like to use it the code still exists in 

Read More

The post ESB-2021.0902 – [SUSE] slurm_20_11 and pdsh: Multiple vulnerabilities appeared first on Malware Devil.



https://malwaredevil.com/2021/03/15/esb-2021-0902-suse-slurm_20_11-and-pdsh-multiple-vulnerabilities/?utm_source=rss&utm_medium=rss&utm_campaign=esb-2021-0902-suse-slurm_20_11-and-pdsh-multiple-vulnerabilities

Barbary Pirates and Russian Cybercrime

In 1801, the United States had a small Navy. Thomas Jefferson deployed almost half that Navy—three frigates and a schooner—to the Barbary C...