Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci(deps): Update dependency PyYAML to v5 [SECURITY] - autoclosed #13

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 6, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
PyYAML (source) ==3.12 -> ==5.4 age adoption passing confidence

⚠️ MAJOR MAJOR MAJOR ⚠️

GitHub Vulnerability Alerts

CVE-2020-14343

A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.


Release Notes

yaml/pyyaml (PyYAML)

v5.4

Compare Source

v5.3.1

Compare Source

v5.3

Compare Source

v5.2

Compare Source

v5.1.2

Compare Source

  • Re-release of 5.1 with regenerated Cython sources to build properly for Python 3.8b2+

v5.1.1

Compare Source

  • Re-release of 5.1 with regenerated Cython sources to build properly for Python 3.8b1

v5.1

Compare Source

  • Re-release of 5.1 with regenerated Cython sources to build properly for Python 3.8b2+

v3.13

Compare Source

  • Resolved issues around PyYAML working in Python 3.7.

Configuration

📅 Schedule: Branch creation - "" in timezone America/Lima, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Jun 6, 2021
@renovate renovate bot force-pushed the renovate/pypi-PyYAML-vulnerability branch from 95512b2 to 953202a Compare August 16, 2021 22:10
@renovate renovate bot force-pushed the renovate/pypi-PyYAML-vulnerability branch from 953202a to 7eb9fed Compare March 8, 2022 19:40
@renovate
Copy link
Contributor Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@renovate renovate bot force-pushed the renovate/pypi-PyYAML-vulnerability branch from 7eb9fed to 45947ce Compare March 25, 2023 02:07
@renovate renovate bot force-pushed the renovate/pypi-PyYAML-vulnerability branch 2 times, most recently from df95627 to 3547c6f Compare May 23, 2023 21:38
@renovate renovate bot force-pushed the renovate/pypi-PyYAML-vulnerability branch from 3547c6f to ce1c6b7 Compare June 17, 2024 18:06
@renovate renovate bot changed the title ci(deps): Update dependency PyYAML to v5 [SECURITY] ci(deps): Update dependency PyYAML to v5 [SECURITY] - autoclosed Aug 6, 2024
@renovate renovate bot closed this Aug 6, 2024
@renovate renovate bot deleted the renovate/pypi-PyYAML-vulnerability branch August 6, 2024 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants