dbcve.org
Add On BuilderPlugin / extension · Splunk

CVE-2023-22943

MEDIUM · 5.3 CVSS v3.1 Published 2023-02-14
Fix available
A fix is available. Upgrade to 3.1.3 / 4.1.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
In Splunk Add-on Builder (AoB) versions below 4.1.2 and the Splunk CloudConnect SDK versions below 3.1.3, requests to third-party APIs through the REST API Modular Input incorrectly revert to using HTTP to connect after a failure to connect over HTTPS occurs.

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 confidence

The REST API Modular Input in Splunk Add-on Builder and CloudConnect SDK has an insecure fallback mechanism where HTTPS connections that fail will downgrade to HTTP, exposing sensitive data to potential interception via plaintext transmission.

MitigationUpgrade Splunk Add-on Builder to version 4.1.2 or higher and CloudConnect SDK to version 3.1.3 or higher to remediate the insecure HTTP fallback behavior.

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
Add On BuilderPlugin / extension
Affected:>= 4.1.0, < 4.1.2
Cloudconnect Software Development KitApplication
Affected:>= 3.1.0, < 3.1.3

CVSS 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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Splunk Add-on Builder version
    Locate the Splunk Add-on Builder app directory (typically $SPLUNK_HOME/etc/apps/splunk_app_addon_builder/) and read the default/app.conf file. Look for the 'version' stanza to find the installed version number.
    Affected if The installed version is 4.1.0, 4.1.1, or any version greater than or equal to 4.1.0 but less than 4.1.2.
  2. Identify CloudConnect SDK version
    Locate the CloudConnect SDK app directory (typically $SPLUNK_HOME/etc/apps/splunk_cloudconnect_sdk/ or similar) and read the default/app.conf file to find the version in the 'version' stanza.
    Affected if The installed version is 3.1.0, 3.1.1, 3.1.2, or any version greater than or equal to 3.1.0 but less than 3.1.3.
  3. Determine if REST API Modular Input is in use
    Search for configured REST API modular inputs in $SPLUNK_HOME/etc/apps/splunk_app_addon_builder/local/ or $SPLUNK_HOME/etc/apps/splunk_cloudconnect_sdk/local/ for inputs.conf files containing 'rest' as the input type, or check the Splunk UI under Inputs > REST API Modular Input to see if any inputs are enabled.
    Affected if Any REST API modular inputs are configured and enabled in either Add-on Builder or CloudConnect SDK.
  4. Inspect REST API input endpoint configuration
    Examine the inputs.conf files for REST API modular inputs (typically under $SPLUNK_HOME/etc/apps/splunk_app_addon_builder/local/inputs.conf or $SPLUNK_HOME/etc/apps/splunk_cloudconnect_sdk/local/inputs.conf). Look for endpoint configuration stanzas and check if 'url' parameters use HTTP URLs or if there are settings related to SSL/HTTPS verification.
    Affected if The REST API modular inputs are configured to connect to endpoints that could trigger an HTTPS failure and fallback to HTTP, or if SSL verification settings are disabled.

You are affected if either Splunk Add-on Builder version is 4.1.0-4.1.1 or CloudConnect SDK version is 3.1.0-3.1.2 AND you have REST API modular inputs configured that may fall back to plaintext HTTP.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.1.3 / 4.1.2 or later
Fixed in 3.1.34.1.2
Interim mitigation

Upgrade Splunk Add-on Builder to version 4.1.2 or higher and CloudConnect SDK to version 3.1.3 or higher to remediate the insecure HTTP fallback behavior.

Recommended fix High confidence

Splunk Add-on Builder 4.1.2 or later; Splunk CloudConnect SDK 3.1.3 or later

  1. Identify the affected Splunk Add-on Builder version in your environment
  2. Identify the affected Splunk CloudConnect SDK version in your environment
  3. For Add-on Builder: Upgrade to version 4.1.2 or later
  4. For CloudConnect SDK: Upgrade to version 3.1.3 or later
  5. Verify the upgrade was successful by checking the version number
  6. Test that REST API Modular Input connections work correctly over HTTPS

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Add On Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22943 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-22943 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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