LiveActive security incident?Get immediate response
CVE Record

CVE-2019-4743: IBM Financial Transaction Manager 3.0 does not set the secure attribute on authorization tokens or session...

IBM Financial Transaction Manager 3.0 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic. IBM X-Force ID: 172880.

MediumCVSS 4.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.0 can send authorization or session cookies over unencrypted HTTP because the Secure cookie attribute is missing. If a user is tricked into visiting an HTTP link, an attacker watching that traffic may capture cookie values and use them to access sensitive application sessions.

Executive priority

Treat this as a moderate-priority session confidentiality issue. It is not cited as actively exploited, but affected financial transaction systems handle sensitive workflows, so confirm exposure and vendor remediation status promptly.

Technical view

The flaw is an insecure cookie configuration in IBM Financial Transaction Manager 3.0. Authorization tokens or session cookies lack the Secure attribute, so browsers may transmit them over HTTP. CVSS 3.0 is 4.3, with network attack vector, low complexity, required user interaction, and low confidentiality impact.

Likely exposure

Exposure is limited to IBM Financial Transaction Manager 3.0 deployments using affected web sessions, especially where HTTP links, redirects, or mixed-content paths can cause cookies to traverse plaintext traffic.

Exploitation context

The source describes user interaction: an attacker sends or plants an HTTP link, then snoops plaintext traffic to obtain cookies. The CVE is not listed as KEV, and the bundle provides no evidence of active exploitation.

Researcher notes

Evidence is clear on root cause and affected version, but the prompt bundle does not include detailed IBM fix instructions. Validation should focus on cookie attributes, HTTP reachability, and whether IBM’s referenced advisory identifies a specific fixed level.

Mitigation direction

  • Review IBM advisory and X-Force entry for official remediation or fixed levels.
  • Prioritize upgrade or vendor-supported configuration changes for IBM FTM 3.0.
  • Reduce plaintext HTTP paths that could receive application cookies.
  • Use HTTPS-only access controls where compatible with vendor guidance.
  • Monitor for suspicious session reuse after HTTP navigation events.

Validation and detection

  • Confirm whether IBM Financial Transaction Manager 3.0 is deployed.
  • Inspect authentication and session Set-Cookie headers for the Secure attribute.
  • Check whether HTTP links or redirects can receive application cookies.
  • Review proxy and TLS termination settings for cookie handling.
  • Document IBM advisory status and applied remediation level.
Prepared
Confidence
medium
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.

cve · low confidence lookup

CVE-2019-4743 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
4.3 (3.0)
Known Exploited
No
Published

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

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
4.3CVSS 3.0MediumCVSS:3.0/UI:R/A:N/S:U/C:L/PR:N/I:N/AV:N/AC:L/RL:O/E:U/RC:C2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

4.3Medium
CVSS 3.0 vector shape for CVE-2019-4743Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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.0Listed
Weakness

CWE details

No CWE listed

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