CVE-2022-48685
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 7.1 before 7.1.2. The daily executed cron file clean_secbi_old_logs is writable by all users and is executed as root, leading to privilege escalation.
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 confidenceA local privilege escalation vulnerability exists in Logpoint 7.1 before 7.1.2 where the cron script clean_secbi_old_logs has world-writable permissions and executes as root. An unprivileged local user can modify this script to gain root privileges.
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.0, < 7.1.2CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 Logpoint installation and versionRun 'dpkg -l | grep logpoint' or 'rpm -qa | grep logpoint' to find the installed Logpoint package and version numberAffected if The installed version is >= 7.1.0 and < 7.1.2
-
Locate the clean_secbi_old_logs cron scriptSearch for the file using 'find / -name clean_secbi_old_logs 2>/dev/null' or check common cron directories like /etc/cron.d/, /etc/cron.daily/, or /var/spool/cron/Affected if The script exists on the system
-
Check file permissions on the scriptRun 'ls -la <path_to_clean_secbi_old_logs>' to view the permission bitsAffected if The file permissions show world-writable access (permissions like 'rwxrwxrwx' or any 'w' in the 'other' section)
-
Verify script ownership and root executionCheck if the file is owned by root and review the script content for root-level commands using 'head -5 <path_to_clean_secbi_old_logs>'Affected if The script runs with root privileges and contains executable commands
A user is affected if Logpoint Siem version 7.1.0 through 7.1.1 is installed AND the clean_secbi_old_logs cron script exists with world-writable permissions, allowing unprivileged modification to execute code as root.
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.2
Update Logpoint to version 7.1.2 or later, or immediately restrict write permissions on the clean_secbi_old_logs cron file to root-only.
7.1.2
- Backup the current Logpoint configuration and any custom configurations
- Review the Logpoint 7.1.2 release notes at servicedesk.logpoint.com for any specific upgrade requirements or migration steps
- Ensure the upgrade is performed during a planned maintenance window
- Upgrade Logpoint SIEM from version 7.1.0 or 7.1.1 to version 7.1.2
- After upgrade, verify the cron file /etc/cron.d/clean_secbi_old_logs (or similar path) now has restricted permissions (should not be world-writable)
- Verify the Logpoint services are running correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48685 — 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-48685 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