CVE-2023-7101: Arbitrary Code Execution (ACE) Vulnerability in gdata

gdata Updated 02 Oct 2025

Summary

16/05/2025
Yes i
Unrated
Not published

CVE-2023-7101: Arbitrary Code Execution (ACE) Vulnerability. Affects gdata versions >= 2.16.1, < 3.0.0. Fixed in 3.0.0. How to fix ↓

Also tracked for

The same CVE-2023-7101 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The gdata package is a component of the CRAN ecosystem and is used for working with data in R. It provides functions for reading and writing data in various formats, including spreadsheets. The vulnerable version of the package is Spreadsheet::ParseExcel version 0.65, which is bundled with gdata. This version allows for the execution of arbitrary code due to the lack of validation on input from a file. The vulnerability specifically affects the evaluation of Number format strings within the Excel parsing logic.

Vulnerability Detail

The arbitrary code execution (ACE) vulnerability in gdata allows an attacker to execute malicious code by exploiting the lack of input validation in the evaluation of Number format strings. By crafting a specially crafted Excel file, an attacker can inject and execute arbitrary code within the context of the application using gdata. This can lead to various consequences, including unauthorized access, data manipulation, and system compromise. The vulnerability has been assigned the CVE identifier CVE-2023-7101.

How To Fix

Minimum fixed version

3.0.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is necessary to upgrade to the fixed version of gdata to mitigate the risk of arbitrary code execution.

Conclusion

The gdata package, specifically the bundled Spreadsheet::ParseExcel version 0.65, is vulnerable to an arbitrary code execution (ACE) vulnerability. This vulnerability can be exploited by an attacker to execute arbitrary code within the application. To mitigate the risk, it is crucial to upgrade gdata to version 3.0.0 or later, which deprecates the vulnerable Excel-related functionality. For more information and support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for gdata →

Share this vulnerability

FAQ

The vulnerability allows an attacker to execute arbitrary code within the context of the application using gdata. This can lead to unauthorized access, data manipulation, and system compromise.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it for open-source vulnerabilities, including CVE-2023-7101.

There are no known public exploits for this vulnerability at the time of writing. However, it is important to upgrade to the fixed version of gdata to prevent potential exploitation.

No, the only way to mitigate the risk is to upgrade to the fixed version of gdata. There are no known workarounds or alternative solutions for this vulnerability.

For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in addressing the vulnerability in your application.

How To Fix

Minimum fixed version

3.0.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback