Loading vulnerability…
CVE-2018-1273 is a remote code injection vulnerability in the Spring Data Commons property binder caused by improper neutralization of special elements in request parameters. It affects the 1.13.x branch through 1.13.10, the 2.0.x branch through 2.0.5, and older unsupported versions. An unauthenticated remote attacker can submit specially crafted parameters to Spring Data REST-backed HTTP resources or applications using Spring Data's projection-based request payload binding, potentially causing remote code execution.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
3 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This 43-file repository is a deliberately vulnerable training environment with a valid manual CVE-2018-1273 exploit, rather than an automated exploitation tool. app/ contains the upstream Compose definition and English/Chinese walkthroughs. Their crafted form POST injects SpEL into a username parameter name and invokes Runtime.exec("touch /tmp/success"). The supplied payload is basic and hardcoded, supporting an OPERATIONAL classification; the challenge mentions obtaining a shell, but no shell payload is included. base/ contains a Maven/Docker build and seven Java source files implementing a Spring Boot user-registration application, plus properties, CSS, and a Thymeleaf template. UserController accepts a proxy-backed UserForm interface, exposing the vulnerable Spring Data binding path before its normal validation. Security auto-configuration is explicitly excluded. The demonstrated effect is server-side command execution, not merely creation of an application user. The template also displays stored BCrypt password hashes in the user listing. isoloom.yml describes one amd64 Spring container on TCP 8080. Generated .isoloom/ files provide Docker, Kubernetes, Vagrant-hosted Docker, Proxmox-hosted Docker, and six cloud deployment variants. Docker removes the target's default route; Kubernetes uses egress policies, whose enforcement depends on the cluster network plugin. Local Docker publishing defaults to loopback, while cloud deployments bind publicly and restrict inbound SSH/web access using an operator-supplied CIDR. These deployment methods are not additional exploit vectors or evidence of container escape. Five shell scripts check page availability, the repeatedPassword form field, and blocked internet access. They do not submit the exploit or verify vulnerability exploitation. GitHub workflows validate generated infrastructure, run lab checks, and register approved labs through secret-configured backend/token URLs. Cleanup commands in provisioning and CI have ordinary infrastructure purposes and do not indicate a fake exploit. Isoloom and Vulhub supply lab orchestration, not an exploit framework. The code-file count includes Java, shell, Ruby, Terraform, Dockerfile, HTML, and CSS files, excluding declarative YAML/JSON/XML configuration. The original analyzed repository URL, git reference, and archive byte size were not supplied; their fields are left empty or zero rather than inferred. UPSTREAM.md identifies the vendored Vulhub source commit as 8fd63916f7a8711e2e01dda0d27237e4d6175d38, which is not necessarily this repository's analyzed revision. Analysis is static; no deployment or exploitation was executed.
This repository is a proof-of-concept (POC) exploit for CVE-2018-1273, a remote code execution vulnerability in Spring Data Commons (prior to 1.13.10 and 2.0.5). The repository contains a minimal Spring Boot application with a vulnerable controller exposing a POST /account endpoint. The exploit leverages improper property binding in Spring Data Commons, allowing an attacker to send a specially crafted POST request with malicious parameters that result in arbitrary code execution on the server. The README provides example curl commands for both Windows and MacOS, demonstrating how to trigger the vulnerability to execute system commands (such as launching the calculator application). The repository includes Java source files for the application and controller, Maven build files, and test scaffolding. This POC is intended for security testing and demonstration of the vulnerability, not for weaponized exploitation.
This repository provides a working proof-of-concept exploit for CVE-2018-1273, a remote code execution vulnerability in Spring Data Commons. The main exploit script is 'cve-2018-1273.py', a Python tool that interacts with a vulnerable Spring Boot application (provided in the 'Vulnerability-environment' directory) via HTTP POST requests. The exploit works by sending a specially crafted parameter to an endpoint (typically '/account'), triggering the vulnerable property binder in Spring Data Commons to execute arbitrary system commands on the server. The repository includes both the exploit script and a full Java-based vulnerable environment for local testing. The exploit is operational, allowing the attacker to specify arbitrary commands to execute on the target. The README files provide detailed usage instructions, example payloads, and endpoint information. The main attack vector is network-based, targeting exposed HTTP endpoints on vulnerable Java applications.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Spring Data Commons remote code execution vulnerability affecting versions prior to 1.13.10 in the 1.13 branch and prior to 2.0.5 in the 2.0 branch, named as one of the exploits used by WatchDog’s scanning/exploitation component.
A remote code execution vulnerability in Spring Data Commons targeted by Satan ransomware to spread to additional hosts.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.