CVE-2022-48587
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 · uneditedA SQL injection vulnerability exists in the “schedule editor” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against the database.
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 SQL injection vulnerability exists in the 'schedule editor' feature of ScienceLogic SL1. The feature accepts unsanitized user-controlled input and directly concatenates it into SQL queries, allowing attackers to inject arbitrary SQL commands that are executed against the database.
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<= 11.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
- 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.
-
Identify installed ScienceLogic SL1 versionAccess the SL1 system administration interface or run: em7_manager --version or check /opt/em7/version file. Alternatively, look at the login page footer or system info page.Affected if The installed version is 11.1.2 or any earlier version (anything <= 11.1.2).
-
Confirm schedule editor feature is enabledNavigate to the SL1 web interface and check if the Schedule Editor feature is accessible. Typically found under the 'Scheduler' or 'Automation' sections in the user menu. Check user permissions to determine if the feature is available to your account.Affected if The schedule editor feature is enabled and accessible to users in your environment.
-
Identify database user and query pathsInspect the backend configuration to locate where SQL queries for the schedule editor are constructed. On the SL1 appliance, examine the web application files under /opt/em7/ for scripts handling the schedule_editor functionality. Look for database connection configurations.Affected if User input from the schedule editor flows directly into SQL query construction without visible sanitization routines.
-
Check for input validation mechanismsExamine the application code or configuration for input validation between the schedule editor UI and database layer. Look for functions that handle schedule names, timestamps, or other user-supplied fields used in scheduling. Check if parameterized queries are implemented.Affected if No input validation/sanitization is found between user input fields in the schedule editor and the SQL query execution layer.
You are affected if your SL1 version is 11.1.2 or earlier AND the schedule editor feature is enabled and accessible to users, with user input being used in SQL queries without proper parameterization.
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 dataImplement parameterized queries (prepared statements) for all database operations in the schedule editor, and apply proper input validation and sanitization to all user-supplied data before using it in SQL queries.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48587 — 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-48587 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