POC详情: b604193ac14afffaab9d467da257e5faa995c246

来源
关联漏洞
标题: Apache Log4j 代码问题漏洞 (CVE-2021-44228)
描述:Apache Log4j是美国阿帕奇(Apache)基金会的一款基于Java的开源日志记录工具。 Apache Log4J 存在代码问题漏洞,攻击者可设计一个数据请求发送给使用 Apache Log4j工具的服务器,当该请求被打印成日志时就会触发远程代码执行。
描述
This powershell script is intended to be used by anyone looking to remediate the Log4j Vulnerability within their environment. It can target multiple machines and run remotely as a job on all or only affected devices.
介绍
<div id="top"></div>
<!--
*** Thanks for checking out the Best-README-Template. If you have a suggestion
*** that would make this better, please fork the repo and create a pull request
*** or simply open an issue with the tag "enhancement".
*** Don't forget to give the project a star!
*** Thanks again! Now go create something AMAZING! :D
-->



<!-- PROJECT SHIELDS -->
<!--
*** I'm using markdown "reference style" links for readability.
*** Reference links are enclosed in brackets [ ] instead of parentheses ( ).
*** See the bottom of this document for the declaration of the reference variables
*** for contributors-url, forks-url, etc. This is an optional, concise syntax you may use.
*** https://www.markdownguide.org/basic-syntax/#reference-style-links
-->
[![Contributors][contributors-shield]][contributors-url]
[![Forks][forks-shield]][forks-url]
[![Stargazers][stars-shield]][stars-url]
[![Issues][issues-shield]][issues-url]
[![GPLv3 License][license-shield]][license-url]



<!-- PROJECT LOGO -->
<br />
<div align="center">
  <a href="https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation">
    <img src="images/log4j-exploit.jpg" alt="Logo" width="80" height="80">
  </a>

<h3 align="center">Log4j CVE-2021-44228 Remediation</h3>

  <p align="center">
    project_description
    <br />
    <a href="https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation"><strong>Explore the docs »</strong></a>
    <br />
    <br />
    <a href="https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation">View Demo</a>
    ·
    <a href="https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation/issues">Report Bug</a>
    ·
    <a href="https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation">Request Feature</a>
  </p>
</div>



<!-- TABLE OF CONTENTS -->
<details>
  <summary>Table of Contents</summary>
  <ol>
    <li>
      <a href="#about-the-project">About The Project</a>
      <ul>
        <li><a href="#built-with">Built With</a></li>
      </ul>
    </li>
    <li>
      <a href="#getting-started">Getting Started</a>
      <ul>
        <li><a href="#prerequisites">Prerequisites</a></li>
        <li><a href="#installation">Installation</a></li>
      </ul>
    </li>
    <li><a href="#usage">Usage</a></li>
    <li><a href="#roadmap">Roadmap</a></li>
    <li><a href="#contributing">Contributing</a></li>
    <li><a href="#license">License</a></li>
    <li><a href="#contact">Contact</a></li>
    <li><a href="#acknowledgments">Acknowledgments</a></li>
  </ol>
</details>



<!-- ABOUT THE PROJECT -->
## About The Project

This powershell script is intended to be used by anyone looking to remediate the Log4j Vulnerability within their environment.
It can target multiple machines and run remotely as a job on all or only affected devices.


<p align="right">(<a href="#top">back to top</a>)</p>



### Built With

* [PowerShell](https://docs.microsoft.com/en-us/powershell/)

<p align="right">(<a href="#top">back to top</a>)</p>



<!-- GETTING STARTED -->
## Getting Started

This is an example of how you may give instructions on setting up your project locally.
To get a local copy up and running follow these simple example steps.

### Prerequisites

You must have the appropriate rights in your environment to run administrative powershell scripts on remote machines.

### Installation

1. Clone the repo or download the PowerShell script
   Clone:
   ```ps
   git clone https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation.git
   ```
   Download Script:
   ```ps
   wget https://raw.githubusercontent.com/digital-dev/Log4j-Remediation/main/Log4j-CVE-2021-44228-Remediation.ps1
   ```
2. Open the script within PowerShell ISE

3. Set the execution policy to allow script execution.
	```ps
	Set-ExecutionPolicy Bypass -Scope CurrentUser
	```

3. Add affected computers to the computer array by editing the "Vulnerable Computers" array.
   ```js
   $vulnerable_computers = @"
	computer-1
	computer-2
	computer-n
	"@
	```

4. Update the location where 7z.exe and 7z.dll are located on an accessible network share within the script.
	```ps
	$7zip_download_location = "\\accessible_networkshare"
	```


<p align="right">(<a href="#top">back to top</a>)</p>



<!-- USAGE EXAMPLES -->
## Usage

Once all of your variables have been set, executing the script will launch a job to automatically go through all listed computers,
and remove the jndilookup.class from all found jar files.



<!-- ROADMAP -->
## Roadmap

- [ ] Add regex matching to only remove jndilookup.class from vulnerable versions of the Log4j package
- [ ] Create a custom object of all computers containing found items and actions performed on found items.

See the [open issues](https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation/issues) for a full list of proposed features (and known issues).

<p align="right">(<a href="#top">back to top</a>)</p>



<!-- CONTRIBUTING -->
## Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are **greatly appreciated**.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement".
Don't forget to give the project a star! Thanks again!

1. Fork the Project
2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)
3. Commit your Changes (`git commit -m 'Add some AmazingFeature'`)
4. Push to the Branch (`git push origin feature/AmazingFeature`)
5. Open a Pull Request

<p align="right">(<a href="#top">back to top</a>)</p>



<!-- LICENSE -->
## License

Distributed under the GPLv3 License. See `LICENSE.txt` for more information.

Project Link: [https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation](https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation)

<p align="right">(<a href="#top">back to top</a>)</p>


<!-- MARKDOWN LINKS & IMAGES -->
<!-- https://www.markdownguide.org/basic-syntax/#reference-style-links -->
[contributors-shield]: https://img.shields.io/github/contributors/digital-dev/Log4j-CVE-2021-44228-Remediation.svg?style=for-the-badge
[contributors-url]: https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation/graphs/contributors
[forks-shield]: https://img.shields.io/github/forks/digital-dev/Log4j-CVE-2021-44228-Remediation.svg?style=for-the-badge
[forks-url]: https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation/network/members
[stars-shield]: https://img.shields.io/github/stars/digital-dev/Log4j-CVE-2021-44228-Remediation.svg?style=for-the-badge
[stars-url]: https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation/stargazers
[issues-shield]: https://img.shields.io/github/issues/digital-dev/Log4j-CVE-2021-44228-Remediation.svg?style=for-the-badge
[issues-url]: https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation/issues
[license-shield]: https://img.shields.io/github/license/digital-dev/Log4j-CVE-2021-44228-Remediation.svg?style=for-the-badge
[license-url]: https://github.com/digital-dev/Log4j-CVE-2021-44228-Remediation/blob/master/LICENSE.txt
文件快照

[4.0K] /data/pocs/b604193ac14afffaab9d467da257e5faa995c246 ├── [5.4K] CODE_OF_CONDUCT.md ├── [4.1K] CONTRIBUTING.md ├── [4.0K] images │   └── [ 43K] log4j-exploit.jpg ├── [ 34K] LICENSE ├── [4.0K] Log4j-CVE-2021-44228-Remediation.ps1 └── [7.0K] README.md 1 directory, 6 files
神龙机器人已为您缓存
备注
    1. 建议优先通过来源进行访问。
    2. 如果因为来源失效或无法访问,请发送邮箱到 f.jinxu#gmail.com 索取本地快照(把 # 换成 @)。
    3. 神龙已为您对POC代码进行快照,为了长期维护,请考虑为本地POC付费,感谢您的支持。