Skip to main content
Public proof of concept

CVE-2023-24107

A public proof of concept exists; no exploitation attested.

  • Published2023-02-22
  • WeaknessCWE-94

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

hour_of_code_python_2015 commit 520929797b9ca43bb818b2e8f963fb2025459fa3 was discovered to contain a code execution backdoor via the request package (requirements.txt). This vulnerability allows attackers to access sensitive user information and execute arbitrary code.

Timeline

dates in UTC
  1. 2023-02-2204:15CVE publishedNVD

Versions per branch

NVD
Hour of code python 2015 project hour of code python 2015
BranchAffectedFixed in
2015.x= 2015-12-11no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2023-02-22
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-35p8-rgfh-rpw2

Frequently asked questions

What is CVE-2023-24107?

hour_of_code_python_2015 commit 520929797b9ca43bb818b2e8f963fb2025459fa3 was discovered to contain a code execution backdoor via the request package (requirements.txt). This vulnerability allows attackers to access sensitive user information and execute arbitrary code.

Is CVE-2023-24107 actively exploited?

A proof-of-concept exploit exists for CVE-2023-24107, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2023-24107?

CVE-2023-24107 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record