pream-totaram

GitHub · Repository owner · Source ID 33207269
Source profile

Source-scoped identity with 1 associated PoC and 1 linked vulnerability.

Showing 1 PoC on this page

GitHub

pream-totaram/CVE-2024-52302-reproduction

Repository PoC0Created 2026-03-25ScannerCVE-2024-5230212 files

25.3 KiB

GitHubPoC details
Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a Spring Boot application that exposes an unvalidated file upload endpoint at payload withheld. It accepts a multipart file and writes it directly to /tmp/ using the original filename, demonstrating the vulnerable endpoint but containing no code to exploit it or generate a malicious payload.

Backdoor review

No backdoor observed in reviewed code

The reviewed text files (mvnw.cmd, pom.xml, CustomerController.java, DemoApplication.java) constitute a standard Spring Boot application with a known unrestricted file upload vulnerability (CVE-2024-52302). The code directly implements the described vulnerability without any concealed backdoor, deceptive payload, or operator-directed harm. The unreviewed binary file 'mvnw' is a standard Maven wrapper and its metadata-only exclusion is a limitation, but the supplied text evidence shows no backdoor behavior.

ClassificationScanner
Model confidence95%
AuthenticationUnknown
LanguagesJava
Target softwarecommon-user-management
Attack typesUnrestricted File Upload
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The code implements the vulnerable endpoint described in CVE-2024-52302 but does not include any exploit payload, attack script, or logic to trigger remote code execution. It only provides the vulnerable application itself, which serves as a target for testing or scanning, not an active exploit.

src/main/java/com/boxing/demo/CustomerController.java:24-31

Requirements

  • The vulnerable endpoint payload withheld must be accessible over the network.src/main/java/com/boxing/demo/CustomerController.java:24-25

Observed behavior

  • The application accepts a multipart file upload via POST to payload withheld.src/main/java/com/boxing/demo/CustomerController.java:24-25
  • The uploaded file is saved to /tmp/ using the original filename without any validation or sanitization.src/main/java/com/boxing/demo/CustomerController.java:27-29
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Vulnerable Endpoint
Payload withheldThe endpoint accepts file uploads without validation, matching the described CVE-2024-52302 vulnerability.src/main/java/com/boxing/demo/CustomerController.java:24-31
Review boundaries

What the analysis did not establish

  • One binary file (mvnw) was flagged but not analyzed; it is a Maven wrapper script and unlikely to contain exploit logic.
  • Only 4 of 12 text files were included; the remaining 8 files are omitted and may contain additional context.
  • The evidence does not include any configuration files (e.g., application.properties) that might show authentication or security settings.
  • One binary file (mvnw, 11790 bytes) was flagged as metadata-only and not analyzed. Its contents could theoretically contain a backdoor, but the associated mvnw.cmd script is a standard Apache Maven Wrapper script and no evidence suggests the binary is malicious.
  • Eight text files were omitted from the evidence packet due to size constraints, so their contents were not reviewed.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.