LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4328: IBM Financial Transaction Manager 3.2.4 is vulnerable to SQL injection.

IBM Financial Transaction Manager 3.2.4 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 177839.

MediumCVSS 6.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

IBM Financial Transaction Manager 3.2.4 has an SQL injection vulnerability. A remote, low-privileged attacker could manipulate database queries to view, add, change, or delete back-end data. This matters most where FTM handles sensitive financial transaction workflows or is reachable from less-trusted networks.

Executive priority

Moderate priority where IBM FTM 3.2.4 is present. The issue can affect financial transaction data integrity and confidentiality, but the available evidence shows low privileges are required and does not confirm active exploitation.

Technical view

CVE-2020-4328 is an SQL injection issue in IBM Financial Transaction Manager 3.2.4. CVSS 3.0 score is 6.3 with network attack vector, low attack complexity, low privileges required, no user interaction, unchanged scope, and low confidentiality, integrity, and availability impacts.

Likely exposure

Exposure is limited to organizations running IBM Financial Transaction Manager 3.2.4. Risk increases where authenticated users, partner connections, or network paths can reach vulnerable FTM functions tied to the back-end database.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The CVSS vector indicates exploitation would be remote and require low privileges, with no user interaction. Public evidence in the bundle does not establish exploit availability or real-world attacks.

Researcher notes

The bundle names only IBM Financial Transaction Manager 3.2.4 as affected. No CWE is supplied, but the vendor description clearly states SQL injection. Do not generalize to other FTM versions without IBM evidence.

Mitigation direction

  • Identify all IBM Financial Transaction Manager 3.2.4 deployments.
  • Review IBM advisory and X-Force entry for official remediation guidance.
  • Apply IBM-provided fixes or mitigations through normal change control.
  • Restrict FTM access to trusted networks and authorized accounts.
  • Monitor application and database logs for abnormal data access or changes.

Validation and detection

  • Confirm installed FTM versions against asset inventory and CMDB records.
  • Verify remediation status using IBM support documentation.
  • Review network exposure for internet, partner, or broad internal access.
  • Check logs for SQL errors or unexpected transaction data changes.
  • Confirm least-privilege access for FTM users and database accounts.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-4328 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.3 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AC:L/C:L/S:U/I:L/A:L/UI:N/AV:N/PR:L/RC:C/RL:O/E:U

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.3CVSS 3.0MediumCVSS:3.0/AC:L/C:L/S:U/I:L/A:L/UI:N/AV:N/PR:L/RC:C/RL:O/E:U2.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

6.3Medium
CVSS 3.0 vector shape for CVE-2020-4328Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AC:L/C:L/S:U/I:L/A:L/UI:N/AV:N/PR:L/RC:C/RL:O/E:U

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMFinancial Transaction Manager3.2.4Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.