LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4729: IBM Safer Payments denial of service

IBM Counter Fraud Management for Safer Payments 5.7.0.00 through 5.7.0.10, 6.0.0.00 through 6.0.0.07, 6.1.0.00 through 6.1.0.05, and 6.2.0.00 through 6.2.1.00 could allow an authenticated attacker under special circumstances to send multiple specially crafted API requests that could cause the application to crash. IBM X-Force ID: 188052.

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

Security readout for executives and security teams

Plain-English summary

This vulnerability can let a logged-in attacker crash IBM Safer Payments by sending multiple specially crafted API requests under specific conditions. The business impact is availability disruption, not data theft or modification based on the supplied CVSS details.

Executive priority

Treat as a targeted availability risk for fraud-payment operations. Prioritize remediation for internet-adjacent, partner-accessible, or high-volume production environments, especially where downtime would affect transaction screening.

Technical view

CVE-2020-4729 affects IBM Counter Fraud Management for Safer Payments versions 5.7.0.00-5.7.0.10, 6.0.0.00-6.0.0.07, 6.1.0.00-6.1.0.05, and 6.2.0.00-6.2.1.00. CVSS 3.1 is 5.3: network reachable, high complexity, low privileges required, no confidentiality or integrity impact, high availability impact.

Likely exposure

Exposure is limited to organizations running the listed IBM Safer Payments versions where authenticated users can reach the affected API surface over the network.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires authentication and special circumstances, reducing likelihood, but successful abuse could crash the application.

Researcher notes

Evidence is limited to CVE, IBM advisory, and X-Force identifiers. No CWE is supplied. The key triage facts are PR:L, AC:H, A:H, and version-specific exposure. Avoid assuming unauthenticated reachability or data compromise.

Mitigation direction

  • Inventory IBM Safer Payments deployments and exact versions.
  • Review IBM advisory 6985595 for supported remediation guidance.
  • Plan upgrade or maintenance to a vendor-confirmed non-affected version.
  • Restrict API access to trusted users and networks where operationally possible.
  • Monitor application crashes and restart patterns around API activity.

Validation and detection

  • Confirm whether deployed versions fall within the listed affected ranges.
  • Verify authenticated API access paths exposed to users or integrations.
  • Review logs for API request bursts followed by application crashes.
  • Confirm IBM advisory remediation status in change records.
  • Retest availability behavior after applying vendor guidance.
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.

cve · low confidence lookup

CVE-2020-4729 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
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H1.63.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2020-4729Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

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
IBMSafer Payments5.7.0.00, 6.0.0.00, 6.1.0.00, 6.2.0.00unaffected
Weakness

CWE details

No CWE listed

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