How many CVEs have patched safe_eval?

1 published CVEs changed safe_eval in run-llama/llama_index, in 1 distinct patches totalling 1 changed lines, between 2023 and 2023.

What is the latest CVE that changed safe_eval?

CVE-2023-39662 (llama-index vulnerable to arbitrary code execution), published 2023-08-15, changed lines 118 of llama_index/exec_utils.py.

How does safe_eval compare to the rest of run-llama/llama_index?

run-llama/llama_index has 26 CVEs with a located fix in total; 1 of them changed safe_eval.

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

run-llama/llama_index

Function

safe_eval

Name: safe_eval in run-llama/llama_index: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

llama_index/exec_utils.py

Last patched August 15, 2023

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

1

Lines changed

Added plus removed

2023

Years

By CVE publication date

Overview

safe_eval in run-llama/llama_index was changed by 1 published CVE fixes in 2023, in 1 distinct patches that added or removed 1 lines in total.

run-llama/llama_index has 26 CVEs with a located fix in total, so 4% of them touched this function.

CVEs that patched it

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

llama-index vulnerable to arbitrary code execution
CVE-2023-39662 · line 118 · +1 −0
Critical · CVSS 9.3
EPSS 1.5%2023-08-15

Get an alert when the next CVE fix lands in run-llama/llama_index, with the patched functions.

Monitor llama_index CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in run-llama/llama_index changed by the most CVE fixes.

default_formatter3 CVEs · llama-index-core/llama_index/core/agent/workflow/react_agent.py load_data2 CVEs · llama-index-integrations/readers/llama-index-readers-obsidian/llama_index/readers/obsidian/base.py get_article_urls2 CVEs · llama-index-integrations/readers/llama-index-readers-web/llama_index/readers/web/knowledge_base/base.py __init__2 CVEs · llama-index-core/llama_index/core/exec_utils.py _verify_source_safety2 CVEs · llama-index-core/llama_index/core/exec_utils.py _restricted_import2 CVEs · llama-index-core/llama_index/core/exec_utils.py

All patched functions in run-llama/llama_index

Frequently asked questions

Common questions about CVE fixes to safe_eval.

How many CVEs have patched safe_eval?: 1 published CVEs changed safe_eval in run-llama/llama_index, in 1 distinct patches totalling 1 changed lines, between 2023 and 2023.
What is the latest CVE that changed safe_eval?: CVE-2023-39662 (llama-index vulnerable to arbitrary code execution), published 2023-08-15, changed lines 118 of llama_index/exec_utils.py.
How does safe_eval compare to the rest of run-llama/llama_index?: run-llama/llama_index has 26 CVEs with a located fix in total; 1 of them changed safe_eval.
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 run-llama/llama_index 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