CVE-2023-49442
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDeserialization of Untrusted Data in jeecgFormDemoController in JEECG 4.0 and earlier allows attackers to run arbitrary code via crafted POST request.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a deserialization vulnerability in the jeecgFormDemoController component of JEECG 4.0 and earlier. The application deserializes untrusted data from POST requests without proper validation, allowing attackers to inject malicious serialized objects that execute arbitrary code on the server (RCE).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify JEECG installed versionLocate the JEECG deployment files or check the version file (often in pom.xml, version.properties, or the WAR file manifest). Run: find /path/to/jeecg -name 'version*' -o -name 'pom.xml' | xargs grep -i version 2>/dev/null, or inspect the WAR file metadata.Affected if The version is 4.0 or lower, or if no version file is found and the application is known to be JEECG 4.0 or earlier.
-
Locate the jeecgFormDemoController endpointSearch the deployed application source code or WAR file for 'jeecgFormDemoController'. Check under src/main/java or the decompiled classes in the WAR. Run: find /path/to/jeecg -type f -name '*jeecgFormDemoController*' 2>/dev/null.Affected if The file jeecgFormDemoController.java or its compiled class exists in the deployment.
-
Verify the endpoint is accessibleSend a POST request to the jeecgFormDemoController endpoint (typically at /jeecgFormDemoController or /controller/jeecgFormDemoController). Use: curl -X POST http://target:port/jeecgFormDemoController -d 'test=1' -v.Affected if The endpoint responds (even with an error) rather than returning 404, indicating the controller is active.
-
Confirm deserialization handling in the controllerInspect the jeecgFormDemoController source code for deserialization operations. Look for ObjectInputStream, readObject, or similar Java deserialization patterns. Search the decompiled class file for keywords: grep -i 'ObjectInputStream\|readObject\|deserialize' jeecgFormDemoController.class.Affected if The code contains deserialization logic that processes POST request data without validation.
You are affected if JEECG version is 4.0 or earlier AND the jeecgFormDemoController endpoint exists and is accessible in your deployment, as this combination enables the unauthenticated deserialization attack.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade JEECG to a version beyond 4.0 that includes the security patch, or if no patched version exists, disable/remove the jeecgFormDemoController endpoint and apply network segmentation to limit exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49442 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-49442 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data