CVE-2021-37304
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 · uneditedAn Insecure Permissions issue in jeecg-boot 2.4.5 allows unauthenticated remote attackers to gain escalated privilege and view sensitive information via the httptrace interface.
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 confidencejeecg-boot 2.4.5 exposes the Spring Boot Actuator httptrace endpoint without authentication, allowing unauthenticated attackers to access HTTP request/response trace data containing sensitive information such as session tokens, cookies, and authorization headers, enabling privilege escalation.
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<= 2.4.5CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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-boot versionCheck your deployed jeecg-boot version by reviewing the pom.xml file, build artifacts, or application startup logs. Look for the version specified in the JeecgBoot dependencies.Affected if The installed version is 2.4.5 or earlier (any version <= 2.4.5).
-
Verify actuator httptrace endpoint is exposedReview your application.properties or application.yml configuration file for properties such as 'management.endpoints.web.exposure.include' or 'management.endpoints.include'. Check if 'httptrace' is listed among the exposed endpoints.Affected if The configuration explicitly includes 'httptrace' in the list of exposed actuator endpoints.
-
Confirm endpoint is accessible without authenticationSend an HTTP GET request to the /httptrace endpoint (for example, http://your-server/actuator/httptrace or http://your-server/actuator/httptrace) using a tool like curl without providing any authentication credentials.Affected if The endpoint returns HTTP 200 OK with trace data containing request/response details without requiring any login or authentication token.
-
Check Spring Security configuration for endpoint protectionReview your Spring Security configuration Java class or XML configuration files to determine if there are security rules that explicitly permit or restrict access to the /actuator/httptrace endpoint. Look for permitAll() or authorizeRequests() configurations related to this endpoint.Affected if The Spring Security configuration does not require authentication for the /httptrace endpoint, or explicitly permits unauthenticated access to it.
You are affected if you are running jeecg-boot version 2.4.5 or lower AND the httptrace actuator endpoint is exposed and accessible without authentication, returning trace data with sensitive headers.
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 dataConfigure Spring Security to require authentication for the /httptrace actuator endpoint, or disable the httptrace endpoint entirely if not needed for production. Review other actuator endpoints for similar exposure.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37304 — 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-2021-37304 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