CVE-2024-56512

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 3.1% (87th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 3.2%CVSS: 5.4Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Apache NiFi 1.10.0 through 2.0.0 are missing fine-grained authorization checking for Parameter Contexts, referenced Controller Services, and referenced Parameter Providers, when creating new Process Groups.

Creating a new Process Group can include binding to a Parameter Context, but in cases where the Process Group did not reference any Parameter values, the framework did not check user authorization for the bound Parameter Context. Missing authorization for a bound Parameter Context enabled clients to download non-sensitive Parameter values after creating the Process Group.

Creating a new Process Group can also include referencing existing Controller Services or Parameter Providers. The framework did not check user authorization for referenced Controller Services or Parameter Providers, enabling clients to create Process Groups and use these components that were otherwise unauthorized.

This vulnerability is limited in scope to authenticated users authorized to create Process Groups. The scope is further limited to deployments with component-based authorization policies. Upgrading to Apache NiFi 2.1.0 is the recommended mitigation, which includes authorization checking for Parameter and Controller Service references on Process Group creation.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity54% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
3.2%
EPSS %ILE
87th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

December 28, 2024

Last Modified

February 11, 2025

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.nifi:nifi-web-api1.10.0 ... 2.0.0-M4 (41 versions)
  • 1.10.0 up to 2.1.0: fixed in 2.1.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 174 total refreshes for this CVE.

  1. 2026-10-10 19:58 UTCEPSS rescore
  2. 2026-10-10 05:03 UTCOSV refresh
  3. 2026-10-09 20:05 UTCEPSS rescore
  4. 2026-10-08 17:08 UTCEPSS rescore
  5. 2026-10-07 23:46 UTCEPSS rescore
  6. 2026-10-06 15:16 UTCEPSS rescore
  7. 2026-10-05 17:41 UTCEPSS rescore
  8. 2026-10-04 23:20 UTCEPSS rescore
  9. 2026-10-03 14:24 UTCEPSS rescore
  10. 2026-10-02 16:24 UTCEG score recompute
  11. 2026-10-01 19:48 UTCEPSS rescore
  12. 2026-09-30 15:02 UTCEPSS rescore
  13. 2026-09-30 15:02 UTCEPSS rescore
  14. 2026-09-28 13:50 UTCEPSS rescore
  15. 2026-09-27 13:44 UTCEPSS rescore
  16. 2026-09-27 13:44 UTCEPSS rescore
  17. 2026-09-26 15:57 UTCEPSS rescore
  18. 2026-09-24 14:01 UTCEPSS rescore
  19. 2026-09-23 13:46 UTCEPSS rescore
  20. 2026-09-22 14:47 UTCEPSS rescore
  21. 2026-09-20 20:14 UTCEPSS rescore
  22. 2026-09-20 20:14 UTCEPSS rescore
  23. 2026-09-20 14:44 UTCOSV refresh
  24. 2026-09-18 19:26 UTCEPSS rescore
  25. 2026-09-16 14:06 UTCEPSS rescore
Show 75 more
  1. 2026-09-16 14:06 UTCEPSS rescore
  2. 2026-09-16 05:12 UTCEPSS rescore
  3. 2026-09-15 03:08 UTCEPSS rescore
  4. 2026-09-12 14:59 UTCEPSS rescore
  5. 2026-09-11 14:51 UTCEPSS rescore
  6. 2026-09-11 09:35 UTCEPSS rescore
  7. 2026-09-10 09:33 UTCEPSS rescore
  8. 2026-09-08 21:59 UTCEPSS rescore
  9. 2026-09-07 16:00 UTCEPSS rescore
  10. 2026-09-06 13:46 UTCEPSS rescore
  11. 2026-09-04 13:59 UTCEPSS rescore
  12. 2026-09-04 05:05 UTCEPSS rescore
  13. 2026-09-02 14:10 UTCEPSS rescore
  14. 2026-09-01 14:54 UTCOSV refresh
  15. 2026-09-01 13:52 UTCEPSS rescore
  16. 2026-08-30 19:16 UTCEPSS rescore
  17. 2026-08-30 19:16 UTCEPSS rescore
  18. 2026-08-30 01:21 UTCEPSS rescore
  19. 2026-08-28 21:39 UTCEPSS rescore
  20. 2026-08-27 14:24 UTCEPSS rescore
  21. 2026-08-26 14:44 UTCEPSS rescore
  22. 2026-08-25 13:47 UTCEPSS rescore
  23. 2026-08-24 14:15 UTCEPSS rescore
  24. 2026-08-23 00:18 UTCEPSS rescore
  25. 2026-08-21 23:47 UTCEPSS rescore
  26. 2026-08-20 22:54 UTCEPSS rescore
  27. 2026-08-19 17:02 UTCEPSS rescore
  28. 2026-08-18 13:47 UTCEPSS rescore
  29. 2026-08-17 13:45 UTCEPSS rescore
  30. 2026-08-16 14:55 UTCEPSS rescore
  31. 2026-08-16 02:13 UTCEPSS rescore
  32. 2026-08-15 16:07 UTCOSV refresh
  33. 2026-08-15 01:29 UTCEPSS rescore
  34. 2026-08-13 21:59 UTCEPSS rescore
  35. 2026-08-12 13:49 UTCEPSS rescore
  36. 2026-08-11 13:41 UTCEPSS rescore
  37. 2026-08-10 23:58 UTCEPSS rescore
  38. 2026-08-09 13:45 UTCEPSS rescore
  39. 2026-08-08 16:35 UTCEPSS rescore
  40. 2026-08-07 16:26 UTCEPSS rescore
  41. 2026-08-06 13:45 UTCEPSS rescore
  42. 2026-08-05 19:16 UTCEPSS rescore
  43. 2026-08-04 15:08 UTCEPSS rescore
  44. 2026-08-03 10:35 UTCEPSS rescore
  45. 2026-08-02 02:25 UTCEPSS rescore
  46. 2026-08-02 02:25 UTCEPSS rescore
  47. 2026-08-01 04:14 UTCEPSS rescore
  48. 2026-07-31 07:42 UTCOSV refresh
  49. 2026-07-30 16:26 UTCEPSS rescore
  50. 2026-07-30 16:26 UTCEPSS rescore
  51. 2026-07-30 01:29 UTCEPSS rescore
  52. 2026-07-28 15:35 UTCEPSS rescore
  53. 2026-07-26 14:53 UTCEPSS rescore
  54. 2026-07-25 14:17 UTCEPSS rescore
  55. 2026-07-25 14:17 UTCEPSS rescore
  56. 2026-07-24 14:16 UTCEPSS rescore
  57. 2026-07-23 14:17 UTCEPSS rescore
  58. 2026-07-23 14:17 UTCEPSS rescore
  59. 2026-07-23 02:45 UTCEG score recompute
  60. 2026-07-22 14:07 UTCEPSS rescore
  61. 2026-07-21 15:23 UTCEPSS rescore
  62. 2026-07-20 17:07 UTCEPSS rescore
  63. 2026-07-19 14:30 UTCEPSS rescore
  64. 2026-07-19 14:30 UTCEPSS rescore
  65. 2026-07-19 02:28 UTCEPSS rescore
  66. 2026-07-19 02:28 UTCEPSS rescore
  67. 2026-07-18 10:03 UTCEPSS rescore
  68. 2026-07-16 17:02 UTCEPSS rescore
  69. 2026-07-15 16:57 UTCEPSS rescore
  70. 2026-07-15 01:59 UTCEPSS rescore
  71. 2026-07-15 01:59 UTCEPSS rescore
  72. 2026-07-13 22:29 UTCEPSS rescore
  73. 2026-07-13 15:08 UTCOSV refresh
  74. 2026-07-13 06:12 UTCEPSS rescore
  75. 2026-07-12 05:45 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCabsholi7ly/CVE-2024-56512-Apache-NiFi-Exploit
    First seen Jan 6, 2025

    A tool to exploit the CVE-2024-56512 vulnerability in Apache NiFi, which allows unauthorized access to sensitive data through improperly secured APIs.

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-56512.yaml
    First seen Jan 1, 2024

    Apache NiFi - Information Disclosure

    Open source ↗

Frequently asked(5)

What is CVE-2024-56512?
CVE-2024-56512 is a medium vulnerability published on December 28, 2024. Apache NiFi 1.10.0 through 2.0.0 are missing fine-grained authorization checking for Parameter Contexts, referenced Controller Services, and referenced Parameter Providers, when creating new Process Groups. Creating a new Process Group can include binding to a Parameter Context, but in cases where…
When was CVE-2024-56512 disclosed?
CVE-2024-56512 was first published on December 28, 2024, with the most recent update on February 11, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-56512 actively exploited?
CVE-2024-56512 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.2% probability of exploitation in the next 30 days (87th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56512?
CVE-2024-56512 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2024-56512?
A fix for CVE-2024-56512 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-56512

Explore →

Is Your Infrastructure Affected by CVE-2024-56512?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.