How many CVEs have patched save?

1 published CVEs changed save in zenml-io/zenml, in 6 distinct patches totalling 31 changed lines, between 2024 and 2024.

What is the latest CVE that changed save?

CVE-2024-2083 (Directory traversal in zenml), published 2024-04-16, changed lines 148 to 409 of src/zenml/materializers/built_in_materializer.py.

How does save compare to the rest of zenml-io/zenml?

zenml-io/zenml has 13 CVEs with a located fix in total; 1 of them changed save.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

zenml-io/zenml

Function

6 files

save

Name: save in zenml-io/zenml: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

Defined in 6 files

Last patched April 16, 2024

1

CVEs

That changed this function

6

Distinct patches

Backports counted once

31

Lines changed

Added plus removed

2024

Years

By CVE publication date

Overview

save in zenml-io/zenml was changed by 1 published CVE fixes in 2024, in 6 distinct patches that added or removed 31 lines in total.

The name occurs in 6 files: src/zenml/materializers/built_in_materializer.py, src/zenml/materializers/cloudpickle_materializer.py, src/zenml/materializers/numpy_materializer.py, src/zenml/materializers/structured_string_materializer.py, src/zenml/materializers/pandas_materializer.py, src/zenml/materializers/service_materializer.py.

zenml-io/zenml has 13 CVEs with a located fix in total, so 8% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed save, newest first, with the lines each fix touched.

Directory traversal in zenml
CVE-2024-2083 · src/zenml/materializers/built_in_materializer.py · lines 148–409 · +7 −5 in 4 hunks
Critical · CVSS 9.9
EPSS 37.5%2024-04-16
Directory traversal in zenml
CVE-2024-2083 · src/zenml/materializers/cloudpickle_materializer.py · lines 97–116 · +2 −1 in 2 hunks
Critical · CVSS 9.9
EPSS 37.5%2024-04-16

Directory traversal in zenml

CVE-2024-2083 · src/zenml/materializers/numpy_materializer.py · lines 106–109 · +4 −1

Critical · CVSS 9.9

EPSS 37.5%2024-04-16

Directory traversal in zenml

CVE-2024-2083 · src/zenml/materializers/pandas_materializer.py · lines 126–134 · +3 −2

Critical · CVSS 9.9

EPSS 37.5%2024-04-16

Directory traversal in zenml

CVE-2024-2083 · src/zenml/materializers/service_materializer.py · lines 64–66 · +2 −1

Critical · CVSS 9.9

EPSS 37.5%2024-04-16

Directory traversal in zenml

CVE-2024-2083 · src/zenml/materializers/structured_string_materializer.py · lines 60–61 · +2 −1

Critical · CVSS 9.9

EPSS 37.5%2024-04-16

Get an alert when the next CVE fix lands in zenml-io/zenml, with the patched functions.

Monitor zenml CVEs

Other functions in these files

Functions in the same files that CVE fixes also changed.

Other hotspots in the repository

Functions in zenml-io/zenml changed by the most CVE fixes.

update_myself3 CVEs · src/zenml/zen_server/routers/users_endpoints.py update_user3 CVEs · src/zenml/zen_server/routers/users_endpoints.py load_model_from_metadata2 CVEs · src/zenml/artifacts/utils.py load2 CVEs · src/zenml/materializers/cloudpickle_materializer.py handle_int_env_var2 CVEs · src/zenml/constants.py get_user2 CVEs · src/zenml/zen_server/routers/users_endpoints.py

All patched functions in zenml-io/zenml

Frequently asked questions

Common questions about CVE fixes to save.

How many CVEs have patched save?: 1 published CVEs changed save in zenml-io/zenml, in 6 distinct patches totalling 31 changed lines, between 2024 and 2024.
What is the latest CVE that changed save?: CVE-2024-2083 (Directory traversal in zenml), published 2024-04-16, changed lines 148 to 409 of src/zenml/materializers/built_in_materializer.py.
How does save compare to the rest of zenml-io/zenml?: zenml-io/zenml has 13 CVEs with a located fix in total; 1 of them changed save.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track zenml-io/zenml CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing