LiveActive security incident?Get immediate response
CVE Record

CVE-2020-4482: IBM UrbanCode Deploy (UCD) 6.2.7.3, 6.2.7.4, 7.0.3.0, and 7.0.4.0 could allow an authenticated user to bypa...

IBM UrbanCode Deploy (UCD) 6.2.7.3, 6.2.7.4, 7.0.3.0, and 7.0.4.0 could allow an authenticated user to bypass security. A user with access to a snapshot could apply unauthorized additional statuses via direct rest calls. IBM X-Force ID: 181856.

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

Security readout for executives and security teams

Plain-English summary

CVE-2020-4482 affects specific IBM UrbanCode Deploy releases. An authenticated user who already has access to a snapshot could bypass intended controls and add unauthorized statuses through direct REST calls. The business impact is integrity loss in deployment governance, not data theft or service outage based on the provided sources.

Executive priority

Prioritize remediation during the next controlled maintenance window if affected versions are present. Escalate sooner where UrbanCode Deploy gates production releases, compliance approvals, or change-management evidence, because unauthorized status changes could undermine release integrity and audit trust.

Technical view

IBM describes a security bypass in UrbanCode Deploy 6.2.7.3, 6.2.7.4, 7.0.3.0, and 7.0.4.0. The flaw requires network access, low privileges, and high attack complexity. The CVSS v3.0 score is 5.3, with high integrity impact and no confidentiality or availability impact.

Likely exposure

Exposure is limited to organizations running the named IBM UrbanCode Deploy versions, especially where many users can access deployment snapshots or REST endpoints. Systems not using IBM UrbanCode Deploy, or not on the listed versions, are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit use, or exploited campaigns. IBM X-Force lists exploit maturity as unproven in the provided CVSS vector. Treat this as an authenticated governance bypass risk rather than an unauthenticated internet-scale emergency.

Researcher notes

Key evidence is narrow: IBM UCD, authenticated user, snapshot access, direct REST calls, unauthorized additional statuses. No CWE is provided. The bundle does not name exact fixed builds, so validation should rely on IBM advisory guidance rather than inferred version targets.

Mitigation direction

  • Identify any IBM UrbanCode Deploy instances and confirm deployed versions.
  • Review IBM advisory 6337603 for vendor remediation and apply supported fixes.
  • Restrict snapshot access to users with a documented operational need.
  • Limit REST API access to trusted networks and authenticated roles.
  • Review deployment status permissions for least-privilege alignment.

Validation and detection

  • Inventory UrbanCode Deploy versions against the affected version list.
  • Confirm vendor remediation status from IBM advisory 6337603.
  • Review audit logs for unexpected snapshot status changes.
  • Validate that users cannot add statuses outside their authorized permissions.
  • Check IAM groups with snapshot access for excessive membership.
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-4482 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.0)
Known Exploited
No
Published

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

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.0MediumCVSS:3.0/C:N/AC:H/PR:L/I:H/A:N/S:U/UI:N/AV:N/RC:C/E:U/RL:O1.63.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

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

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

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
IBMUrbanCode Deploy6.2.7.3, 7.0.3.0, 7.0.4.0, 6.2.7.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.