Nifi Minifi C\+\+Application · Apache
CVE-2021-33191
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 · uneditedFrom Apache NiFi MiNiFi C++ version 0.5.0 the c2 protocol implements an "agent-update" command which was designed to patch the application binary. This "patching" command defaults to calling a trusted binary, but might be modified to an arbitrary value through a "c2-update" command. Said command is then executed using the same privileges as the application binary. This was addressed in version 0.10.0
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 confidenceIn Apache NiFi MiNiFi C++ 0.5.0+, the c2 protocol's 'agent-update' command allows arbitrary code execution. Attackers can modify the trusted binary path via the 'c2-update' command, then trigger 'agent-update' to execute their controlled binary with the same privileges as the MiNiFi application (typically elevated).
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
>= 0.5.0, < 0.10.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 MiNiFi C++ versionLocate the MiNiFi C++ executable or check its build version (commonly via --version flag or looking at installed binaries/package metadata)Affected if Version is 0.5.0 or higher but below 0.10.0
-
Locate c2 protocol configurationSearch the MiNiFi C++ configuration directory (typically the 'conf' folder) for c2-related settings in the properties file (often named minifi.properties or similar)Affected if C2 protocol is explicitly configured or enabled in the configuration files
-
Verify c2 protocol network exposureExamine the c2 configuration for binding addresses and ports. Check if the c2 listener (often configured under 'nifi.c2.*' properties) is bound to an IP address accessible from untrusted networksAffected if C2 listener is bound to a wildcard address (0.0.0.0) or an externally accessible IP without network segmentation or authentication in place
Environment is affected if MiNiFi C++ version is between 0.5.0 and 0.10.0 AND the c2 protocol is enabled and accessible to untrusted network actors.
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 · scoped0.10.0
Upgrade to MiNiFi C++ version 0.10.0 or later where this vulnerability is patched. Additionally, restrict network access to c2 protocol endpoints to prevent unauthorized attackers from sending malicious c2-update commands.
0.10.0
- Identify the current Apache NiFi MiNiFi C++ version in use by checking the application binary or configuration
- Plan an upgrade to version 0.10.0 or later
- Back up all existing configuration files and data directories
- Test the upgrade in a non-production environment first
- Deploy the upgrade to production systems
- Verify the c2 protocol agent-update functionality works correctly after upgrade
- Ensure no unauthorized c2-update commands can modify the patching command
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Nifi Minifi C\+\+
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33191 — 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-2021-33191 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