CVE-2022-48684
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 issue was discovered in Logpoint before 7.1.1. Template injection was seen in the search template. The search template uses jinja templating for generating dynamic data. This could be abused to achieve code execution. Any user with access to create a search template can leverage this to execute code as the loginspect user.
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 confidenceLogpoint before 7.1.1 contains a Server-Side Template Injection (SSTI) vulnerability in the search template feature. The application uses Jinja templating to generate dynamic data without proper input sanitization, allowing authenticated users with search template creation privileges to escape the template context and execute arbitrary code as the loginspect user.
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< 7.1.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Determine installed Logpoint Siem versionAccess the Logpoint administration interface and navigate to System > About, or run the command 'lpctl version' from the Logpoint server shell to retrieve the exact version numberAffected if The version is lower than 7.1.1 (for example, 7.0.0, 6.x, or any version below 7.1.1)
-
Verify search template feature accessibilityLog into Logpoint as a regular user and navigate to the Search Templates section in the UI, or check if the /api/search-template endpoint is accessible via APIAffected if The search template feature is available and accessible to the user account being tested
-
Identify users with search template creation privilegesIn Logpoint admin UI, go to Users > Roles and examine role permissions, or query the user configuration for any role containing 'template' or 'search_template' creation rightsAffected if Any user account other than fully trusted administrators has permission to create or modify search templates
-
Audit existing search templates for injection payloadsExport all search templates via Logpoint API (GET /api/search-template) or manually review each template in the UI, looking for Jinja2 syntax like {{, }}, {%, or base64/encoded strings that may indicate code execution attemptsAffected if Any search template contains unusual Jinja2 expressions, code-like syntax, or suspicious variable references not originating from your organization
-
Review logs for suspicious template-related activitySearch Logpoint's internal logs (using Logpoint itself) for events containing 'search-template', 'template', or 'jinja' around the time of potential exploitation, and check for commands executed by the 'loginspect' userAffected if Logs show template creation/modification with code-like content, or unexpected command execution by the loginspect user
You are affected if your Logpoint Siem version is below 7.1.1 AND any user (even low-privilege) has access to the search template feature with creation privileges, or if you detect modified templates or suspicious activity in logs.
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.
dbcve · scoped7.1.1
Upgrade to Logpoint 7.1.1 or later. Until then, restrict search template creation privileges to only trusted administrators and monitor for suspicious template content.
Logpoint SIEM 7.1.1 or later
- Backup all Logpoint configurations, custom searches, and templates before proceeding with the upgrade.
- Review Logpoint upgrade documentation at servicedesk.logpoint.com for your specific deployment type.
- Schedule a maintenance window as upgrades may require system downtime.
- Upgrade the Logpoint SIEM installation to version 7.1.1 or later.
- After upgrade, verify the search template functionality is working correctly.
- Audit user permissions and restrict who can create or modify search templates to only necessary personnel.
- Verify the fix by confirming Jinja template rendering is sandboxed and no longer allows arbitrary code execution.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48684 — 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-2022-48684 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