CVE-2023-28937
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 · uneditedDataSpider Servista version 4.4 and earlier uses a hard-coded cryptographic key. DataSpider Servista is data integration software. ScriptRunner and ScriptRunner for Amazon SQS are used to start the configured processes on DataSpider Servista. The cryptographic key is embedded in ScriptRunner and ScriptRunner for Amazon SQS, which is common to all users. If an attacker who can gain access to a target DataSpider Servista instance and obtain a Launch Settings file of ScriptRunner and/or ScriptRunner for Amazon SQS, the attacker may perform operations with the user privilege encrypted in the file. Note that DataSpider Servista and some of the OEM products are affected by this vulnerability. For the details of affected products and versions, refer to the information listed in [References].
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 confidenceDataSpider Servista version 4.4 and earlier embeds a hard-coded cryptographic key in ScriptRunner and ScriptRunner for Amazon SQS components. This key is common across all deployments. An attacker who gains access to the target system and obtains a Launch Settings file can decrypt the encrypted user privileges stored within, allowing them to perform operations with the compromised user's 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<= 4.2= 4.3= 4.4CVSS 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.
-
Check DataSpider Servista versionLocate and inspect the DataSpider Servista installation directory. Look for version information in the product's about dialog, release notes, or version file (commonly found in the installation root or in a version/info file within the product directory structure)Affected if The installed version is 4.2 or earlier, or exactly 4.3, or exactly 4.4
-
Identify ScriptRunner component usageDetermine if ScriptRunner or ScriptRunner for Amazon SQS components are installed and in use. Check the product's component list, installed modules, or configuration directories for these specific componentsAffected if ScriptRunner or ScriptRunner for Amazon SQS components are present and configured in the installation
-
Locate Launch Settings filesSearch for Launch Settings files (commonly named with patterns like 'launch' or 'settings' in the DataSpider installation directory, typically under a 'settings' or 'config' subdirectory)Affected if Launch Settings files exist in the installation directory and are accessible to users who should not have access
-
Inspect ScriptRunner configuration for embedded keyExamine ScriptRunner configuration files (typically XML or properties files within the ScriptRunner component directory) for the presence of a hardcoded cryptographic key string. Search for patterns like 'key', 'crypt', 'encrypt', or a 16+ character alphanumeric string that appears static across deploymentsAffected if A hardcoded cryptographic key is found in ScriptRunner configuration files and is the same across different installations
A user is affected if DataSpider Servista version 4.4 or earlier is installed with ScriptRunner or ScriptRunner for Amazon SQS components, and the system contains accessible Launch Settings files with a hardcoded encryption key.
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 · scopedApply vendor patches when available. In the meantime, strictly limit access to DataSpider Servista systems and protect Launch Settings files from unauthorized access, as the file theft combined with system access enables privilege escalation.
DataSpider Servista version 4.4.1 or later (verify exact fixed version from vendor advisory)
- Check the official DataSpider Servista release notes or security advisory on cs.wingarc.com for the fixed version number
- Identify the OEM products listed in the references that may also be affected by this vulnerability
- Upgrade DataSpider Servista to the version that removes the hard-coded cryptographic key (version 4.4.1 or later, if available)
- After upgrading, regenerate any stored credentials or encrypted files that may have used the hard-coded key
- If a newer version is not available, contact the vendor (Wingarc or HULFT) for a patch or specific remediation guidance
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28937 — 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-28937 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