CVE-2018-14572: conference-scheduler-cli - Arbitrary Code Execution

conference-scheduler-cli Updated 02 Oct 2025

Summary

28/08/2018
No i
High
7.8

CVE-2018-14572: In conference-scheduler-cli, a pickle.load call on imported data allows remote attackers to execute arbitrary code via a crafted .pickle file, as demonstrated by Python code that contains an os.system call. Affects conference-scheduler-cli versions 0.1.0 – 0.9.1. No fix is published. How to fix ↓

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

conference-scheduler-cli is a Python package available on PyPI that provides functionality for scheduling conferences. It allows users to import and manage conference data, including speakers, sessions, and schedules. The package is widely used in the Python community for organizing and managing conferences.

Vulnerability Detail

The vulnerability (CVE-2018-14572) in conference-scheduler-cli arises from a pickle.load call on imported data. This allows remote attackers to execute arbitrary code by crafting a malicious .pickle file. An attacker can exploit this vulnerability by injecting Python code into the .pickle file, which may include commands to execute system-level operations. The impact of this vulnerability is significant as it allows an attacker to execute arbitrary code on the target system, potentially leading to unauthorized access, data breaches, or further compromise of the system.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, as a general best practice, it is recommended to exercise caution when importing and processing untrusted data. Implementing input validation and sanitization techniques can help mitigate the risk of code injection vulnerabilities.

Conclusion

In conclusion, the conference-scheduler-cli package is vulnerable to arbitrary code execution due to a pickle.load call on imported data. This vulnerability can be mitigated by updating to the latest version of the package and exercising caution when importing untrusted data. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for conference-scheduler-cli →

Share this vulnerability

FAQ

conference-scheduler-cli is a Python package used for managing conference data and scheduling. It is widely used in the Python community for organizing conferences.

The vulnerability allows remote attackers to execute arbitrary code on the target system, potentially leading to unauthorized access, data breaches, or further compromise of the system.

To fix this vulnerability, it is recommended to update conference-scheduler-cli to the latest version that includes a patch for this issue. Additionally, validate any imported .pickle files for potential malicious content before loading them into the application.

While there is no specific workaround mentioned for this vulnerability, implementing input validation and sanitization techniques can help mitigate the risk of code injection vulnerabilities.

For more information about this vulnerability, you can refer to the CVE-2018-14572 identifier or the advisory database source provided in the vulnerability details.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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