ID CVE-2019-3816
Summary Openwsman, versions up to and including 2.6.9, are vulnerable to arbitrary file disclosure because the working directory of openwsmand daemon was set to root directory. A remote, unauthenticated attacker can exploit this vulnerability by sending a specially crafted HTTP request to openwsman server.
Vulnerable Configurations
  • OpenWSMAN Project OpenWSMAN 2.6.9
  • RedHat Enterprise Linux Desktop 7.0
  • RedHat Enterprise Linux Server 7.0
  • Red Hat Enterprise Linux Server Advanced mission critical Update Support (AUS) 7.6
  • Red Hat Enterprise Linux Server Extended Update Support (EUS) 7.6
  • Red Hat Enterprise Linux Server Telecommunications Update Service (TUS) 7.6
  • RedHat Enterprise Linux Workstation 7.0
  • Fedora 28
  • Fedora 29
  • Fedora 30
  • openSUSE Leap 15.0
  • openSUSE Leap 42.3
Base: 5.0
  • Subverting Environment Variable Values
    The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
  • Footprinting
    An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Browser Fingerprinting
    An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
redhat via4
  • bugzilla
    id 1667070
    title CVE-2019-3816 openwsman: Disclosure of arbitrary files outside of the registered URIs
    • OR
      • comment Red Hat Enterprise Linux 7 Client is installed
        oval oval:com.redhat.rhba:tst:20150364001
      • comment Red Hat Enterprise Linux 7 Server is installed
        oval oval:com.redhat.rhba:tst:20150364002
      • comment Red Hat Enterprise Linux 7 Workstation is installed
        oval oval:com.redhat.rhba:tst:20150364003
      • comment Red Hat Enterprise Linux 7 ComputeNode is installed
        oval oval:com.redhat.rhba:tst:20150364004
    • OR
      • AND
        • comment libwsman-devel is earlier than 0:2.6.3-6.git4391e5c.el7_6
          oval oval:com.redhat.rhsa:tst:20190638009
        • comment libwsman-devel is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20190638010
      • AND
        • comment libwsman1 is earlier than 0:2.6.3-6.git4391e5c.el7_6
          oval oval:com.redhat.rhsa:tst:20190638013
        • comment libwsman1 is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20190638014
      • AND
        • comment openwsman-client is earlier than 0:2.6.3-6.git4391e5c.el7_6
          oval oval:com.redhat.rhsa:tst:20190638015
        • comment openwsman-client is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20190638016
      • AND
        • comment openwsman-perl is earlier than 0:2.6.3-6.git4391e5c.el7_6
          oval oval:com.redhat.rhsa:tst:20190638005
        • comment openwsman-perl is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20190638006
      • AND
        • comment openwsman-python is earlier than 0:2.6.3-6.git4391e5c.el7_6
          oval oval:com.redhat.rhsa:tst:20190638007
        • comment openwsman-python is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20190638008
      • AND
        • comment openwsman-ruby is earlier than 0:2.6.3-6.git4391e5c.el7_6
          oval oval:com.redhat.rhsa:tst:20190638011
        • comment openwsman-ruby is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20190638012
      • AND
        • comment openwsman-server is earlier than 0:2.6.3-6.git4391e5c.el7_6
          oval oval:com.redhat.rhsa:tst:20190638017
        • comment openwsman-server is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20190638018
    id RHSA-2019:0638
    released 2019-03-25
    severity Important
    title RHSA-2019:0638: openwsman security update (Important)
  • rhsa
    id RHSA-2019:0972
  • libwsman-devel-0:2.6.3-6.git4391e5c.el7_6
  • libwsman1-0:2.6.3-6.git4391e5c.el7_6
  • openwsman-client-0:2.6.3-6.git4391e5c.el7_6
  • openwsman-perl-0:2.6.3-6.git4391e5c.el7_6
  • openwsman-python-0:2.6.3-6.git4391e5c.el7_6
  • openwsman-ruby-0:2.6.3-6.git4391e5c.el7_6
  • openwsman-server-0:2.6.3-6.git4391e5c.el7_6
refmap via4
  • 107368
  • 107409
  • FEDORA-2019-348166f7fd
  • FEDORA-2019-64b384de9b
  • FEDORA-2019-af0cd1b8f7
  • openSUSE-SU-2019:1111
  • openSUSE-SU-2019:1217
Last major update 14-03-2019 - 18:29
Published 14-03-2019 - 18:29
Last modified 07-05-2019 - 03:29
Back to Top