ReversingLabs-TitaniumCloud v2: Other - Update version of ReversingLabs SDK and dependency libraries due to known vulnerabilities

[DinkoReversingLabs]

Please ensure your pull request (PR) adheres to the following guidelines:

• Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist

Please check if your PR fulfills the following requirements:

• Testing of all the changes has been performed (for bug fixes / features)
• The manual_readme_content.md has been reviewed and added / updated if needed (for bug fixes / features)
• Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
• Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
• Verify all checks are passing.
• Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
• Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type

Please check the type of change your PR introduces:

• New App
• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Documentation
• Other (please describe): Update on libraries which contain security vulnerabilities reported

Security Considerations (REQUIRED)

• If you are exposing any endpoints using a REST handler,
  please document them in the manual_readme_content.md.
• If this is a new connector or you are adding new actions
  • Please document in the manual_readme_content.md all methods (eg, OAuth) used to authenticate
    with the service that the connector is integrating with.
  • If any actions are unable to run on SOAR Cloud, please document this in the manual_readme_content.md.
• Are you introducing any new cryptography modules? If yes, please elaborate their purpose:
• Are you are accessing the file system? If yes, please verify that you are only accessing paths returned through
  the Vault API.
• Are you are marking code to be ignored by Semgrep with nosemgrep?
  If yes, please provide justification in an additional comment next to the ignored code.

Release Notes (REQUIRED)

• Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

What is the current behavior? (OPTIONAL)

• Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

• Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

• Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

• Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

---

Thanks for contributing!

[splunk-soar-connectors-bot]

@DinkoReversingLabs Static Tests results for commit ff4a634 - https://drive.google.com/file/d/1GnNbAkVNAh5zjIYy8VwAGD7infI4yS_H/view?usp=drivesdk

[splunk-soar-connectors-bot]

@DinkoReversingLabs Compile Tests results for commit ff4a634 - https://drive.google.com/file/d/19yDWEk7pqIlHVnywt82d6nG0T9Ev-UPa/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Static Tests results for commit a1afee2 - https://drive.google.com/file/d/1ZqgPCpW8YcJ_NNsVtFos5x-KjFeFJzqw/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Compile Tests results for commit a1afee2 - https://drive.google.com/file/d/16x7YAjgBsQTv_XeJo-9-Ueu9S8IjRIc5/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Static Tests results for commit c024a73 - https://drive.google.com/file/d/1oxyFB0mWXvhTl9vkwU4THNl7eWuo7NOS/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Compile Tests results for commit c024a73 - https://drive.google.com/file/d/1YqOg7GJnJLPAe8AIeLlvKa3zt5DpZv5R/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Static Tests results for commit b68d3d2 - https://drive.google.com/file/d/1fr2Fem0sqOWnUXUdHxa7nxGcoJ81MBQC/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Compile Tests results for commit b68d3d2 - https://drive.google.com/file/d/1lLrbndpgt1ZfLuT2eXDletMK2XnQxe4T/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Static Tests results for commit 0328c74 - https://drive.google.com/file/d/1dCQB-tWTKAO5Q_WzTT_pjj0jrsxiOGz2/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Compile Tests results for commit 0328c74 - https://drive.google.com/file/d/10xPubSLnVA0YFs-1ej7KmDe1AG3o7S4W/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Static Tests results for commit c8ad76d - https://drive.google.com/file/d/1Egm7lHrr8ktbKfpcGA01YlXHnStCsq5E/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Compile Tests results for commit c8ad76d - https://drive.google.com/file/d/1uG2mFqNoAvL1e6YjzyxqqJcGss7if4rI/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Static Tests results for commit 6313519 - https://drive.google.com/file/d/1huvHM5u_c5UqRfwaYLqJgvqw_t7hPI5M/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Compile Tests results for commit 6313519 - https://drive.google.com/file/d/1xA1T7QMOo-0256xY38aw6KWmApnDu_ZH/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Static Tests results for commit ebb8a4c - https://drive.google.com/file/d/1xovYom8rn70WIg19wTMdNEBC4dhw20YX/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Compile Tests results for commit ebb8a4c - https://drive.google.com/file/d/1RaRTiBCGdwDWKSKiNz_5mZpHhCF4NcHH/view?usp=drivesdk

[DinkoReversingLabs]

@mishalp-crest @ishans-crest

We are having an issue with deploying newly added changes to repo due to linting in your github action. I have tried to replicate steps from github actions with same python version and config from https://github.com/phantomcyber/dev-cicd-tools

In our case sorting (isort) and formatting (black) exclude each other. Changes that apply these tool on code prevents pipeline. If you try to add suggested changes from one tool it breaks the other tool.

Could you check outputs from pipeline execution and help us with this issue.

Kind regards
Dinko

[ishans-crest]

@mishalp-crest @ishans-crest

We are having an issue with deploying newly added changes to repo due to linting in your github action. I have tried to replicate steps from github actions with same python version and config from https://github.com/phantomcyber/dev-cicd-tools

In our case sorting (isort) and formatting (black) exclude each other. Changes that apply these tool on code prevents pipeline. If you try to add suggested changes from one tool it breaks the other tool.

Could you check outputs from pipeline execution and help us with this issue.

Kind regards Dinko

Thanks for reaching out, this is known issue. We are fixing it and releasing a new patch soon.

[DinkoReversingLabs]

out, this is known issue. We are fixing it and releasing a new patch soon.

Hi @ishans-crest,

do you have some ETA on fix? We would like to plan this release notification and other activities related to the updated connector.

Kind regards
Dinko

[splunk-soar-connectors-bot]

@integrationsbot Static Tests results for commit 8efe7e0 - https://drive.google.com/file/d/1RE9b3zipEIxx2SOWuLj2kVWx1d0N3lvh/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Compile Tests results for commit 8efe7e0 - https://drive.google.com/file/d/1X-XdMX4fBJc9MWRaipq9FyJA88hotP8Z/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Static Tests results for commit 659eb1d - https://drive.google.com/file/d/1ZcMYXI_5a5UiEQY-wbinyeteRsP3WWgg/view?usp=drivesdk

[splunk-soar-connectors-bot]

@integrationsbot Compile Tests results for commit 659eb1d - https://drive.google.com/file/d/1vk9UYtcA2X8HUG99GwqZL6geNNATm7ql/view?usp=drivesdk