dbcve.org
FireflowApplication · Algosec

CVE-2023-46595

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Net-NTLM leak via HTML injection in FireFlow VisualFlow workflow editor allows an attacker to obtain victim’s domain credentials and Net-NTLM hash which can lead to relay domain attacks. Fixed in A32.20 (b570 or above), A32.50 (b390 or above)

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 · moderate confidence

HTML injection vulnerability in FireFlow VisualFlow workflow editor allows attackers to inject malicious content that triggers the victim's browser to perform NTLM authentication. When the victim views the injected content, the Net-NTLM hash is leaked to the attacker, enabling relay attacks against domain services.

MitigationApply the vendor-provided patches: upgrade to A32.20 (build 570 or above) or A32.50 (build 390 or above). Additionally, consider disabling Net-NTLM/NetBIOS authentication at the network level if feasible.

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
FireflowApplication
Affected:= a32.20= a32.50= a32.60

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 if Algosec Fireflow is installed
    Locate the Fireflow installation directory or check system services for Algosec Fireflow components
    Affected if Algosec Fireflow software is present on the system
  2. Determine the installed Fireflow version and build number
    Access the Fireflow administration interface or check version files in the installation directory to retrieve the exact version (a32.20, a32.50, or a32.60) and build number
    Affected if The installed version is a32.20, a32.50, or a32.60 with a build number below 570 for a32.20 or below 390 for a32.50 (a32.60 appears fully affected)
  3. Verify if VisualFlow workflow editor is accessible
    Check whether the VisualFlow workflow editor module is enabled and accessible to users through the Fireflow web interface
    Affected if VisualFlow editor is enabled and accessible to users or attackers
  4. Inspect workflow configurations for suspicious content
    Review existing workflow definitions and templates in the Fireflow database or configuration files for any unexpected HTML script tags, img tags with external sources, or links to UNC paths that could trigger NTLM authentication
    Affected if Any workflow contains injected content designed to trigger NTLM authentication requests

Users are affected if they run Algosec Fireflow versions a32.20, a32.50, or a32.60 with builds below the patched levels and have the VisualFlow editor accessible, as this enables HTML injection leading to Net-NTLM hash leakage.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided patches: upgrade to A32.20 (build 570 or above) or A32.50 (build 390 or above). Additionally, consider disabling Net-NTLM/NetBIOS authentication at the network level if feasible.

Recommended fix Moderate confidence

A32.20 (b570+) or A32.50 (b390+) or latest A32.x stable release

  1. 1. Identify the current installed version of Fireflow (A32.20, A32.50, or A32.60) and its build number
  2. 2. If running A32.20 series, upgrade to build 570 or higher
  3. 3. If running A32.50 series, upgrade to build 390 or higher
  4. 4. If running A32.60 series, upgrade to the latest available stable release
  5. 5. After upgrade, verify the VisualFlow workflow editor is functioning correctly
  6. 6. Test that HTML injection is no longer possible in the workflow editor fields

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

Fix this in Fireflow Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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