evil-winrm 3.3 → 3.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a5b4d19083e34991e2462c30c5e702d63adcb9f4196c83dad55f72bc28d49912
-  data.tar.gz: 9ec7bbf0b9ab35d924f174a5c959278b9155637ffa6afa5f435b9c9cfd202591
+  metadata.gz: 6be773e9a859c1ec758e56edd5649d9ab4946401fcb7be836af797b4dc45fa74
+  data.tar.gz: ba1f49a3d8dd68161d76f3b6836eb435775098a534dcc00338110b7a33d7b9ea
 SHA512:
-  metadata.gz: a8cee0b0166a7c72fa1f5e1d0acc99df8e7e0a055cd6977bf51f3824675a9bd8c6379fa2dd9b7d4092046ab5fb490884f965b7377e078575be179d1861f38811
-  data.tar.gz: c621e579753526ce2430fd8424e99f43832129be92c232140cbaf19d5461118f58878bc839109ce28cf0cbb16a7341a6a4feb3f023a7ece121415cfd6fce903e
+  metadata.gz: 3a66b6ff33f83106584f84aa4a090cc2859fb373ed85ffcb2a11ed5d77c35ee22486cb983baac350340fc3006810ef5dacdf1917e149cefb77bd115dcb12e4c1
+  data.tar.gz: 5370fb20f60f0bb3db080ddc949a79c95b542c4a657e1a4003d32ba1634bbb98a443f157288a8d06f491478eb5c938c6088249aff5f9b4262444b280e04e658f

data/.editorconfig

@@ -0,0 +1,21 @@
+#EditorConfig: http://editorconfig.org
+
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+
+[*.{rb,md}]
+indent_style = space
+indent_size = 4
+trim_trailing_whitespace = true
+
+[Gemfile]
+indent_style = space
+indent_size = 4
+
+[Dockerfile]
+indent_style = space
+indent_size = 4

data/CHANGELOG.md

@@ -0,0 +1,94 @@
+### 3.4
+ - Added CI files to be used in Github actions for Docker automated building
+ - Improvements on dynamic AMSI bypass
+ - Added gemspec file to repo for gem building
+
+### 3.3
+ - Fixed missing output messages for Invoke-Binary
+ - Extracted AMSI bypass from menu to avoid menu problems due to M$ AV signatures
+ - Dynamic AMSI bypass implemented to avoid AV signatures
+
+### 3.2
+ - Fixed minor duplicated code problem
+ - Dockerfile improvements
+ - AMSI bypass update
+
+### 3.1
+ - Version released just to quick fix ruby dependencies on gem
+
+### 3.0
+ - Remote files/directories autocomplete feature
+ - Added option to log commands and outputs to a log file (Thanks to Borch Cañavate)
+
+### 2.4
+ - File permission access error now handled in exception to avoid losing connection
+ - Improvements on bundler installation method
+ - Added spn (Service Principal Names) option param for kerberos auth to set some different than default HTTP
+ - Fixed prompt colors (ANSI)
+
+### 2.3
+ - Fixed Invoke-Binary arguments
+ - Service function improved, now show privileges over the services
+
+### 2.2
+ - Added progress bar for file uploads/downloads
+ - New ascii art on menu
+ - Name of Dll loader refactored
+ - Help added to Invoke-Binary
+ - Fixed Invoke-Binary to accept any number of arguments separated by commas
+
+### 2.1
+ - Fixed required params for certificates auth
+ - Removed trailing spaces for better visualization
+ - Added command line option to disable colors
+ - Improved Windows compatibility
+ - Trap capturing to avoid accidental shell exit on Ctrl+C
+
+### 2.0
+ - Fix GSSAPI error
+ - Docker support added
+
+### 1.9
+ - Added AMSI bypass
+ - Fix the ps1 load with large size
+ - Kerberos auth support
+ - Improve upload/download functionality
+
+### 1.8
+ - Added pass-the-hash feature
+ - Added bundler installation method
+
+### 1.7
+ - Added x64 compatibility to use Donut payloads
+
+### 1.6
+ - Added SSL and certificates support
+ - Upload/download messages improved
+ - Updated documentation
+ - Removed scripts and executables dir as mandatory arguments
+ - Added logo
+
+### 1.5
+ - Refactor to class
+ - Fixed upload/download error
+ - Added help arguments for connection
+
+### 1.4
+ - Small fixes
+
+### 1.3
+ - Added colors to shell prompt
+ - Added images to documentation
+
+### 1.2
+ - Added some validations
+ - Added badges to documentation
+
+### 1.1
+ - Translation to english
+ - Added first documentation
+ - Added colors for messages
+ - First ruby gem created
+
+### 1.0
+ - Initial commit

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at oscar.alfonso.diaz@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

data/CONTRIBUTING.md

@@ -0,0 +1,22 @@
+# Contributing
+
+Hello, thank you for your interest into contributing to this project. Your help is really appreciated.
+
+Please note we have a [Code of Conduct], please follow it in all your interactions with the project.
+
+---
+
+## Git Workflow Policy
+
+1. Direct push to [Master] is not allowed.
+2. Pull Requests to [Master] are not allowed.
+3. Usually, commits and pull requests should be done on [Dev] branch. If you have any doubt, don't hesitate to ask first.
+4. Temporary branches may be existing for specific features, be pretty sure that the branch you are going to commit on is the right one. Ask first if you have any doubt.
+5. Any branch will be finally merged to [Dev], there it will be reviewed and tested deeply before being merged to [Master].
+6. All merges from [Dev] to [Master] are a new `evil-winrm` release. This merges to [Master] will be performed and reviewed exclusively by the staff.
+
+---
+
+[Code of Conduct]: CODE_OF_CONDUCT.md
+[Master]: https://github.com/Hackplayers/evil-winrm/tree/master
+[Dev]: https://github.com/Hackplayers/evil-winrm/tree/dev

data/Dockerfile

@@ -0,0 +1,64 @@
+# Evil-WinRM Dockerfile
+
+# Base image
+FROM ruby:latest
+
+# Credits & Data
+LABEL \
+    name="Evil-WinRM" \
+    author="CyberVaca <cybervaca@gmail.com>" \
+    maintainer="OscarAkaElvis <oscar.alfonso.diaz@gmail.com>" \
+    description="The ultimate WinRM shell for hacking/pentesting"
+
+#Env vars
+ENV EVILWINRM_URL="https://github.com/Hackplayers/evil-winrm.git"
+
+# Install dependencies
+RUN gem install \
+    winrm \
+    winrm-fs \
+    stringio \
+    logger \
+    fileutils
+
+# Create volume for powershell scripts
+RUN mkdir /ps1_scripts
+VOLUME /ps1_scripts
+
+# Create volume for executable files
+RUN mkdir /exe_files
+VOLUME /exe_files
+
+# Create volume for data (upload/download)
+RUN mkdir /data
+VOLUME /data
+
+# Set workdir
+WORKDIR /opt/
+
+#Evil-WinRM install method 1 (only one method can be used, other must be commented)
+#Install Evil-WinRM (Docker Hub automated build process)
+RUN mkdir evil-winrm
+COPY . /opt/evil-winrm
+
+#Evil-WinRM install method 2 (only one method can be used, other must be commented)
+#Install Evil-WinRM (manual image build)
+#Uncomment git clone line and one of the ENV vars to select branch (master->latest, dev->beta)
+#ENV BRANCH="master"
+#ENV BRANCH="dev"
+#RUN git clone -b ${BRANCH} ${EVILWINRM_URL}
+
+# Make script file executable
+RUN chmod +x evil-winrm/*.rb
+
+# Clean and remove useless files
+RUN rm -rf /opt/evil-winrm/resources > /dev/null 2>&1 && \
+    rm -rf /opt/evil-winrm/.github > /dev/null 2>&1 && \
+    rm -rf /opt/evil-winrm/CONTRIBUTING.md > /dev/null 2>&1 && \
+    rm -rf /opt/evil-winrm/CODE_OF_CONDUCT.md > /dev/null 2>&1 && \
+    rm -rf /opt/evil-winrm/Dockerfile > /dev/null 2>&1 && \
+    rm -rf /opt/evil-winrm/Gemfile* > /dev/null 2>&1 && \
+    rm -rf /tmp/* > /dev/null 2>&1
+
+# Start command (launching Evil-WinRM)
+ENTRYPOINT ["/opt/evil-winrm/evil-winrm.rb"]

data/Gemfile

@@ -0,0 +1,3 @@
+source 'https://rubygems.org'
+
+gemspec

data/LICENSE

@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.