Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
  • Support the projectPage
Back

CVE-2016-0373

IBM UrbanCode Deploy 6.0 through 6.2.2.1 could allow an authenticated user to read sensitive information due to UCD REST endpoints not…

Description

IBM UrbanCode Deploy 6.0 through 6.2.2.1 could allow an authenticated user to read sensitive information due to UCD REST endpoints not properly authorizing users when determining who can read data. IBM X-Force ID: 112119.

Timeline

  1. ID reserved

    By ibm

  2. · 3 years later

    Published

  3. · 6 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2016-0373, by who scored it
Scored byCVSSScoreVector
ibmCNA (assigner)3.0Low3.1CVSS:3.0/A:N/AC:H/AV:N/C:L/I:N/PR:L/S:U/UI:N/E:U/RC:C/RL:O
NVDNVD · Modified3.0Medium4.3CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS (exploitation in 30 days)
0.78% · top 44% of all CVEs (9 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 3.1.

Affected products

  • IBM · UrbanCode Deploy

    • affected 6.1.0.2
    • affected 6.0
    • affected 6.0.1
    • affected 6.0.1.1
    • affected 6.0.1.2
    • affected 6.0.1.3
    • affected 6.0.1.4
    • affected 6.0.1.5
    • affected 6.0.1.6
    • affected 6.1
    • affected 6.1.0.1
    • affected 6.1.0.3
    • affected 6.0.1.7
    • affected 6.0.1.8
    • affected 6.1.0.4
    • affected 6.1.1
    • affected 6.1.1.1
    • affected 6.1.1.2
    • affected 6.1.1.3
    • affected 6.1.1.4
    • affected 6.1.1.5
    • affected 6.0.1.9
    • affected 6.1.1.6
    • affected 6.1.1.7
    • affected 6.1.2
    • affected 6.0.1.10
    • affected 6.0.1.11
    • affected 6.1.1.8
    • affected 6.1.3
    • affected 6.1.3.1
    • affected 6.2
    • affected 6.2.0.1
    • affected 6.0.1.12
    • affected 6.1.3.2
    • affected 6.2.0.2
    • affected 6.2.1
    • affected 6.0.1.13
    • affected 6.2.1.1
    • affected 6.0.1.14
    • affected 6.1.3.3
    • and 2 more

References

2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2016-0373 badge
[![CVE-2016-0373](https://cveledger.app/badge/CVE-2016-0373.svg)](https://cveledger.app/cve/CVE-2016-0373)

Record last updated .