Review for errors and add auto execute and connect back functionality

.gitignore

@@ -0,0 +1,28 @@
+# Compiled object files
+*.o
+
+# Compiled binary files
+CVE-2021-1965-poc
+
+# Logs
+*.log
+
+# Temporary files
+*.tmp
+*.swp
+
+# Backup files
+*.bak
+*.old
+
+# Dependency directories
+node_modules/
+vendor/
+
+# Build directories
+build/
+dist/
+
+# System files
+.DS_Store
+Thumbs.db

CHANGELOG.md

@@ -0,0 +1,9 @@
+# Changelog
+
+## [Unreleased]
+- Add new feature X
+- Fix bug Y
+- Improve performance of Z
+
+## [1.0.0] - 2022-01-01
+- Initial release

CODE_OF_CONDUCT.md

@@ -0,0 +1,42 @@
+# Code of Conduct
+
+## Purpose
+
+The purpose of this Code of Conduct is to foster a positive and inclusive community for all contributors and maintainers. We are committed to providing a welcoming and respectful environment for everyone, regardless of their background or experience.
+
+## Our Standards
+
+We expect all community members to adhere to the following standards:
+
+- Use welcoming and inclusive language
+- Be respectful of differing viewpoints and experiences
+- Gracefully accept constructive criticism
+- Focus on what is best for the community
+- Show empathy towards other community members
+
+## Unacceptable Behavior
+
+The following behaviors are not tolerated in our community:
+
+- Harassment, discrimination, or offensive comments
+- Trolling, insulting, or derogatory remarks
+- Publishing private information without consent
+- Any other conduct that could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for enforcing this Code of Conduct and addressing any issues that arise. They have the authority to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that do not align with this Code of Conduct.
+
+## Scope
+
+This Code of Conduct applies to all project spaces, including issue trackers, pull requests, and other communication channels. It also applies when an individual is representing the project or its community in public spaces.
+
+## Enforcement
+
+If you witness or experience any violations of this Code of Conduct, please report them to the project maintainers at [[email protected]](mailto:[email protected]). All reports will be reviewed and investigated promptly and fairly.
+
+Maintainers are obligated to maintain the confidentiality and privacy of the reporter. Actions taken in response to a violation may include a warning, temporary or permanent ban, or other appropriate measures.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0, available at [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).

CONTRIBUTING.md

@@ -0,0 +1,30 @@
+# Contributing to CVE-2021-1965
+
+Thank you for considering contributing to this project! To contribute, please follow these guidelines:
+
+## Getting Started
+
+1. Fork the repository and create a new branch for your changes.
+2. Ensure your code follows the existing style and conventions.
+3. Write clear and concise commit messages.
+
+## Code Guidelines
+
+1. Add comments to your code to improve readability and maintainability.
+2. Include unit tests to verify your changes.
+3. Update the `README.md` file if your changes affect the usage or setup of the project.
+4. Ensure your changes do not introduce new security vulnerabilities.
+
+## Submitting a Pull Request
+
+1. Submit a pull request with a detailed description of your changes and the problem they solve.
+2. Be responsive to feedback and make necessary revisions to your pull request.
+
+## Additional Notes
+
+1. Please ensure your code follows the existing style and conventions.
+2. Add comments to your code to improve readability and maintainability.
+3. Include unit tests to verify your changes.
+4. Update the `README.md` file if your changes affect the usage or setup of the project.
+5. Ensure your changes do not introduce new security vulnerabilities.
+6. Be responsive to feedback and make necessary revisions to your pull request.