dbcve.org
Nifi Minifi C\+\+Application · Apache

CVE-2023-41180

MEDIUM · 5.9 CVSS v3.1 Published 2023-09-03
Fix available
A fix is available. Upgrade to after 0.14.0 or later.
See remediation →
68/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
Incorrect certificate validation in InvokeHTTP on Apache NiFi MiNiFi C++ versions 0.13 to 0.14 allows an intermediary to present a forged certificate during TLS handshake negotation. The Disable Peer Verification property of InvokeHTTP was effectively flipped, disabling verification by default, when using HTTPS. Mitigation: Set the Disable Peer Verification property of InvokeHTTP to true when using MiNiFi C++ versions 0.13.0 or 0.14.0. Upgrading to MiNiFi C++ 0.15.0 corrects the default behavior.

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

Apache NiFi MiNiFi C++ versions 0.13 through 0.14 have a certificate validation flaw in the InvokeHTTP processor where TLS peer verification was incorrectly disabled by default when using HTTPS connections. This allows man-in-the-middle attackers to intercept encrypted traffic using forged certificates.

MitigationUpgrade to MiNiFi C++ 0.15.0 or later to restore proper certificate validation defaults, or explicitly configure the Disable Peer Verification property appropriately for your security requirements when using affected versions.

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
Nifi Minifi C\+\+Application
Affected:>= 0.13.0, <= 0.14.0

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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 MiNiFi C++ version
    Check the installed MiNiFi C++ version using the binary, command line (--version or -v), or inspect the manifest/configuration files included with the installation
    Affected if The installed version is >= 0.13.0 and <= 0.14.0
  2. Locate InvokeHTTP processor usage
    Search flow configuration files (typically YAML-based flow.yml or similar) for any InvokeHTTP processor definitions in your MiNiFi deployment
    Affected if The InvokeHTTP processor is present in any flow configuration
  3. Check for HTTPS usage in InvokeHTTP
    In the InvokeHTTP processor configuration, inspect the URL property to determine if HTTPS is being used (URL starts with https://)
    Affected if The InvokeHTTP processor is configured with an HTTPS URL
  4. Inspect peer verification setting
    In the InvokeHTTP processor configuration, check the 'Disable Peer Verification' property or equivalent TLS verification setting
    Affected if Disable Peer Verification is set to true, or the setting is absent/unset while using HTTPS (which causes default-disabled verification in affected versions)

A user is affected if they run MiNiFi C++ version 0.13.0 through 0.14.0 and have configured the InvokeHTTP processor to make HTTPS requests with peer verification disabled or left at the default setting.

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 a release after 0.14.0
Interim mitigation

Upgrade to MiNiFi C++ 0.15.0 or later to restore proper certificate validation defaults, or explicitly configure the Disable Peer Verification property appropriately for your security requirements when using affected versions.

Recommended fix High confidence

MiNiFi C++ 0.15.0

  1. 1. Plan and schedule downtime for the MiNiFi C++ agent upgrade.
  2. 2. Back up current MiNiFi C++ configuration files, particularly flow definitions and properties files.
  3. 3. Download Apache MiNiFi C++ 0.15.0 from the official Apache repository (https://archive.apache.org/dist/nifi/minifi-cpp/).
  4. 4. Install MiNiFi C++ 0.15.0 on the target systems, preserving custom configurations.
  5. 5. Verify that the InvokeHTTP processor's default behavior now correctly validates TLS certificates (Disable Peer Verification defaults to false).
  6. 6. Test HTTPS connections from InvokeHTTP to ensure proper certificate validation is functioning.
  7. 7. Monitor logs for any certificate validation errors and confirm successful TLS handshakes.
Caveat Review release notes for 0.15.0 for any changes to processor behavior, configuration defaults, or API changes that may affect existing flows.

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

Fix this in Nifi Minifi C\+\+ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41180 — 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-41180 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