nday
CVE-2020-7030

IPO Information Disclosure

Avaya / IP Office

A public PoC appeared 9 days after disclosure. nday has no fix record for it yet; that does not mean no patch exists. Listed by 1 of 4 PoC sources: exploitdb. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

cryptographic failure
CWE-522, stated by the CNA avaya and NVD, republishing [email protected]
information disclosure
CWE-200, stated by NVD's analysts
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (CVSS 3.1) from the CNA avaya
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (CVSS 3.1) from the CNA avaya
Exploit-DB
Exploit-DB entries 48581
stage
POC
disclosed
disclosure → PoC
T+9d POC is date-only
cvss
5.5 MEDIUM v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2020-06-03T23:45Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
2020-06-12, date only
ITWexploited
no record yet
KEVKEV
no record yet

Summary

A sensitive information disclosure vulnerability was discovered in the web interface component of IP Office that may potentially allow a local user to gain unauthorized access to the component. Affected versions of IP Office include: 9.x, 10.0 through 10.1.0.7 and 11.0 though 11.0.4.3.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

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

CVSS 3.1 vector from the CVE record, scored by the CNA avaya.

Event log

+DISdisclosed

CVE record published by avaya. CVSS 5.5, medium.

src cvelist · nday , bulk import · raw
{
  "id": 64444,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2020-7030",
  "occurred_at": "2020-06-03T23:45:14.497Z",
  "observed_at": "2026-11-12T21:04:12.541754Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
      "version": "3.1",
      "base_score": 5.5,
      "base_severity": "MEDIUM"
    },
    "state": "PUBLISHED",
    "date_published": "2020-06-03T23:45:14.497Z",
    "assigner_short_name": "avaya"
  }
}
2020-06-12date only, from source
+POCpublic PoC

Exploit-DB lists public exploit code “Avaya IP Office 11 - Password Disclosure” (EDB-48581).

src exploitdb 48581 · nday , bulk import · raw
{
  "id": 27644,
  "type": "poc_published",
  "source": "exploitdb",
  "url": "https://www.exploit-db.com/exploits/48581",
  "occurred_at": "2020-06-12T00:00:00Z",
  "observed_at": "2026-11-12T15:24:40.221206Z",
  "is_backfill": true,
  "dedupe_key": "48581",
  "detail": {
    "url": "https://www.exploit-db.com/exploits/48581",
    "file": "exploits/multiple/webapps/48581.txt",
    "kind": "exploit",
    "tags": [],
    "type": "webapps",
    "title": "Avaya IP Office 11 - Password Disclosure",
    "author": "hyp3rlinx",
    "edb_id": 48581,
    "cve_ids": [
      "CVE-2020-7030"
    ],
    "platform": "multiple",
    "verified": false,
    "precision": "day",
    "confidence": "curated",
    "date_added": "2020-06-12",
    "date_updated": "2020-06-12",
    "date_published": "2020-06-12"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.