ID CVE-2019-10153
Summary A flaw was discovered in fence-agents, prior to version 4.3.4, where using non-ASCII characters in a guest VM's comment or other fields would cause fence_rhevm to exit with an exception. In cluster environments, this could lead to preventing automated recovery or otherwise denying service to clusters of which that VM is a member.
References
Vulnerable Configurations
  • cpe:2.3:a:clusterlabs:fence-agents:-:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:-:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.6:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.6:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.7:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.7:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.8:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.8:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.9:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.9:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.10:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.10:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.11:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.11:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.1.12:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.1.12:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.9.5:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.9.5:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.9.6:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.9.6:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.9.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.9.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:3.9.8:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:3.9.8:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.10:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.10:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.11:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.11:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.12:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.12:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.13:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.13:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.14:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.14:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.15:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.15:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.16:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.16:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.17:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.17:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.18:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.18:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.19:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.19:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.20:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.20:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.21:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.21:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.22:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.22:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.23:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.23:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.24:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.24:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.0.25:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.0.25:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:clusterlabs:fence-agents:4.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:clusterlabs:fence-agents:4.3.3:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux_server:7.0:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux_server:7.0:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux_workstation:7.0:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux_workstation:7.0:*:*:*:*:*:*:*
CVSS
Base: 4.0 (as of 09-10-2019 - 23:44)
Impact:
Exploitability:
CWE CWE-172
CAPEC
  • Postfix, Null Terminate, and Backslash
    If a string is passed through a filter of some kind, then a terminal NULL may not be valid. Using alternate representation of NULL allows an attacker to embed the NULL mid-string while postfixing the proper data so that the filter is avoided. One example is a filter that looks for a trailing slash character. If a string insertion is possible, but the slash must exist, an alternate encoding of NULL in mid-string may be used.
  • Using Unicode Encoding to Bypass Validation Logic
    An attacker may provide a Unicode string to a system component that is not Unicode aware and use that to circumvent the filter or cause the classifying mechanism to fail to properly understanding the request. That may allow the attacker to slip malicious data past the content filter and/or possibly cause the application to route the request incorrectly.
  • Using Slashes and URL Encoding Combined to Bypass Validation Logic
    This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.
  • Embedding NULL Bytes
    An attacker embeds one or more null bytes in input to the target software. This attack relies on the usage of a null-valued byte as a string terminator in many environments. The goal is for certain components of the target software to stop processing the input when it encounters the null byte(s).
  • Using Escaped Slashes in Alternate Encoding
    This attack targets the use of the backslash in alternate encoding. An attacker can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the attacker tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.
  • URL Encoding
    This attack targets the encoding of the URL. An attacker can take advantage of the multiple way of encoding an URL and abuse the interpretation of the URL. An URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc. The attacker could also subvert the meaning of the URL string request by encoding the data being sent to the server through a GET request. For instance an attacker may subvert the meaning of parameters used in a SQL request and sent through the URL string (See Example section).
  • Using UTF-8 Encoding to Bypass Validation Logic
    This attack is a specific variation on leveraging alternate encodings to bypass validation logic. This attack leverages the possibility to encode potentially harmful input in UTF-8 and submit it to applications not expecting or effective at validating this encoding standard making input filtering difficult. UTF-8 (8-bit UCS/Unicode Transformation Format) is a variable-length character encoding for Unicode. Legal UTF-8 characters are one to four bytes long. However, early version of the UTF-8 specification got some entries wrong (in some cases it permitted overlong characters). UTF-8 encoders are supposed to use the "shortest possible" encoding, but naive decoders may accept encodings that are longer than necessary. According to the RFC 3629, a particularly subtle form of this attack can be carried out against a parser which performs security-critical validity checks against the UTF-8 encoded form of its input, but interprets certain illegal octet sequences as characters.
  • Double Encoding
    The adversary utilizes a repeating of the encoding process for a set of characters (that is, character encoding a character encoding of a character) to obfuscate the payload of a particular request. This may allow the adversary to bypass filters that attempt to detect illegal characters or strings, such as those that might be used in traversal or injection attacks. Filters may be able to catch illegal encoded strings, but may not catch doubly encoded strings. For example, a dot (.), often used in path traversal attacks and therefore often blocked by filters, could be URL encoded as %2E. However, many filters recognize this encoding and would still block the request. In a double encoding, the % in the above URL encoding would be encoded again as %25, resulting in %252E which some filters might not catch, but which could still be interpreted as a dot (.) by interpreters on the target.
  • Leverage Alternate Encoding
    An adversary leverages the possibility to encode potentially harmful input or content used by applications such that the applications are ineffective at validating this encoding standard.
  • Using Leading 'Ghost' Character Sequences to Bypass Input Filters
    Some APIs will strip certain leading characters from a string of parameters. An adversary can intentionally introduce leading "ghost" characters (extra characters that don't affect the validity of the request at the API layer) that enable the input to pass the filters and therefore process the adversary's input. This occurs when the targeted API will accept input data in several syntactic forms and interpret it in the equivalent semantic way, while the filter does not take into account the full spectrum of the syntactic forms acceptable to the targeted API.
Access
VectorComplexityAuthentication
NETWORK LOW SINGLE
Impact
ConfidentialityIntegrityAvailability
NONE NONE PARTIAL
cvss-vector via4 AV:N/AC:L/Au:S/C:N/I:N/A:P
redhat via4
advisories
bugzilla
id 1716286
title CVE-2019-10153 fence-agents: mis-handling of non-ASCII characters in guest comment fields
oval
OR
  • comment Red Hat Enterprise Linux must be installed
    oval oval:com.redhat.rhba:tst:20070304026
  • AND
    • comment Red Hat Enterprise Linux 7 is installed
      oval oval:com.redhat.rhba:tst:20150364027
    • OR
      • AND
        • comment fence-agents-aliyun is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037001
        • comment fence-agents-aliyun is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037002
      • AND
        • comment fence-agents-all is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037003
        • comment fence-agents-all is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037004
      • AND
        • comment fence-agents-amt-ws is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037005
        • comment fence-agents-amt-ws is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037006
      • AND
        • comment fence-agents-apc is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037007
        • comment fence-agents-apc is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037008
      • AND
        • comment fence-agents-apc-snmp is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037009
        • comment fence-agents-apc-snmp is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037010
      • AND
        • comment fence-agents-aws is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037011
        • comment fence-agents-aws is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037012
      • AND
        • comment fence-agents-azure-arm is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037013
        • comment fence-agents-azure-arm is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037014
      • AND
        • comment fence-agents-bladecenter is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037015
        • comment fence-agents-bladecenter is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037016
      • AND
        • comment fence-agents-brocade is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037017
        • comment fence-agents-brocade is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037018
      • AND
        • comment fence-agents-cisco-mds is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037019
        • comment fence-agents-cisco-mds is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037020
      • AND
        • comment fence-agents-cisco-ucs is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037021
        • comment fence-agents-cisco-ucs is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037022
      • AND
        • comment fence-agents-common is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037023
        • comment fence-agents-common is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037024
      • AND
        • comment fence-agents-compute is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037025
        • comment fence-agents-compute is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037026
      • AND
        • comment fence-agents-drac5 is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037027
        • comment fence-agents-drac5 is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037028
      • AND
        • comment fence-agents-eaton-snmp is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037029
        • comment fence-agents-eaton-snmp is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037030
      • AND
        • comment fence-agents-emerson is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037031
        • comment fence-agents-emerson is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037032
      • AND
        • comment fence-agents-eps is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037033
        • comment fence-agents-eps is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037034
      • AND
        • comment fence-agents-gce is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037035
        • comment fence-agents-gce is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037036
      • AND
        • comment fence-agents-heuristics-ping is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037037
        • comment fence-agents-heuristics-ping is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037038
      • AND
        • comment fence-agents-hpblade is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037039
        • comment fence-agents-hpblade is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037040
      • AND
        • comment fence-agents-ibmblade is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037041
        • comment fence-agents-ibmblade is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037042
      • AND
        • comment fence-agents-ifmib is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037043
        • comment fence-agents-ifmib is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037044
      • AND
        • comment fence-agents-ilo-moonshot is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037045
        • comment fence-agents-ilo-moonshot is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037046
      • AND
        • comment fence-agents-ilo-mp is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037047
        • comment fence-agents-ilo-mp is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037048
      • AND
        • comment fence-agents-ilo-ssh is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037049
        • comment fence-agents-ilo-ssh is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037050
      • AND
        • comment fence-agents-ilo2 is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037051
        • comment fence-agents-ilo2 is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037052
      • AND
        • comment fence-agents-intelmodular is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037053
        • comment fence-agents-intelmodular is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037054
      • AND
        • comment fence-agents-ipdu is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037055
        • comment fence-agents-ipdu is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037056
      • AND
        • comment fence-agents-ipmilan is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037057
        • comment fence-agents-ipmilan is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037058
      • AND
        • comment fence-agents-kdump is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037059
        • comment fence-agents-kdump is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037060
      • AND
        • comment fence-agents-lpar is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037061
        • comment fence-agents-lpar is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037062
      • AND
        • comment fence-agents-mpath is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037063
        • comment fence-agents-mpath is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037064
      • AND
        • comment fence-agents-redfish is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037065
        • comment fence-agents-redfish is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037066
      • AND
        • comment fence-agents-rhevm is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037067
        • comment fence-agents-rhevm is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037068
      • AND
        • comment fence-agents-rsa is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037069
        • comment fence-agents-rsa is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037070
      • AND
        • comment fence-agents-rsb is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037071
        • comment fence-agents-rsb is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037072
      • AND
        • comment fence-agents-sbd is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037073
        • comment fence-agents-sbd is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037074
      • AND
        • comment fence-agents-scsi is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037075
        • comment fence-agents-scsi is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037076
      • AND
        • comment fence-agents-virsh is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037077
        • comment fence-agents-virsh is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037078
      • AND
        • comment fence-agents-vmware-rest is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037079
        • comment fence-agents-vmware-rest is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037080
      • AND
        • comment fence-agents-vmware-soap is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037081
        • comment fence-agents-vmware-soap is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037082
      • AND
        • comment fence-agents-wti is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037083
        • comment fence-agents-wti is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037084
      • AND
        • comment fence-agents-zvm is earlier than 0:4.2.1-24.el7
          oval oval:com.redhat.rhsa:tst:20192037085
        • comment fence-agents-zvm is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20192037086
rhsa
id RHSA-2019:2037
released 2019-08-06
severity Moderate
title RHSA-2019:2037: fence-agents security, bug fix, and enhancement update (Moderate)
rpms
  • fence-agents-aliyun-0:4.2.1-24.el7
  • fence-agents-all-0:4.2.1-24.el7
  • fence-agents-amt-ws-0:4.2.1-24.el7
  • fence-agents-apc-0:4.2.1-24.el7
  • fence-agents-apc-snmp-0:4.2.1-24.el7
  • fence-agents-aws-0:4.2.1-24.el7
  • fence-agents-azure-arm-0:4.2.1-24.el7
  • fence-agents-bladecenter-0:4.2.1-24.el7
  • fence-agents-brocade-0:4.2.1-24.el7
  • fence-agents-cisco-mds-0:4.2.1-24.el7
  • fence-agents-cisco-ucs-0:4.2.1-24.el7
  • fence-agents-common-0:4.2.1-24.el7
  • fence-agents-compute-0:4.2.1-24.el7
  • fence-agents-debuginfo-0:4.2.1-24.el7
  • fence-agents-drac5-0:4.2.1-24.el7
  • fence-agents-eaton-snmp-0:4.2.1-24.el7
  • fence-agents-emerson-0:4.2.1-24.el7
  • fence-agents-eps-0:4.2.1-24.el7
  • fence-agents-gce-0:4.2.1-24.el7
  • fence-agents-heuristics-ping-0:4.2.1-24.el7
  • fence-agents-hpblade-0:4.2.1-24.el7
  • fence-agents-ibmblade-0:4.2.1-24.el7
  • fence-agents-ifmib-0:4.2.1-24.el7
  • fence-agents-ilo-moonshot-0:4.2.1-24.el7
  • fence-agents-ilo-mp-0:4.2.1-24.el7
  • fence-agents-ilo-ssh-0:4.2.1-24.el7
  • fence-agents-ilo2-0:4.2.1-24.el7
  • fence-agents-intelmodular-0:4.2.1-24.el7
  • fence-agents-ipdu-0:4.2.1-24.el7
  • fence-agents-ipmilan-0:4.2.1-24.el7
  • fence-agents-kdump-0:4.2.1-24.el7
  • fence-agents-lpar-0:4.2.1-24.el7
  • fence-agents-mpath-0:4.2.1-24.el7
  • fence-agents-redfish-0:4.2.1-24.el7
  • fence-agents-rhevm-0:4.2.1-24.el7
  • fence-agents-rsa-0:4.2.1-24.el7
  • fence-agents-rsb-0:4.2.1-24.el7
  • fence-agents-sbd-0:4.2.1-24.el7
  • fence-agents-scsi-0:4.2.1-24.el7
  • fence-agents-virsh-0:4.2.1-24.el7
  • fence-agents-vmware-rest-0:4.2.1-24.el7
  • fence-agents-vmware-soap-0:4.2.1-24.el7
  • fence-agents-wti-0:4.2.1-24.el7
  • fence-agents-zvm-0:4.2.1-24.el7
refmap via4
confirm
Last major update 09-10-2019 - 23:44
Published 30-07-2019 - 23:15
Last modified 09-10-2019 - 23:44
Back to Top