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

14 results

Back

CVE-2019-5254

Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace…

Description

Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981) have an out-of-bounds read vulnerability. An attacker who logs in to the board may send crafted messages from the internal network port or tamper with inter-process message packets to exploit this vulnerability. Due to insufficient validation of the message, successful exploit may cause the affected board to be abnormal.

Timeline

  1. ID reserved

    By huawei

  2. · 11 months later

    Published

  3. · 5 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-2019-5254, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High8.6CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.74% · top 45% of all CVEs (11 Nov 2026)
Loading the EPSS history…

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

Affected products

  • AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981

    • affected V200R005C30
    • affected V200R006C10
    • affected V200R006C20
    • affected V200R007C10
    • affected V200R007C20
    • affected V200R008C00
    • affected V200R008C10
    • affected V200R009C00
    • affected V500R001C00SPC300
    • affected V500R001C00SPC500
    • affected V500R001C00SPH303
    • affected V500R001C00SPH508
    • affected V500R001C20
    • affected V500R001C20SPC100
    • affected V500R001C20SPC100PWE
    • affected V500R001C20SPC200
    • affected V500R001C20SPC200B062
    • affected V500R001C20SPC200PWE
    • affected V500R001C20SPC300B078
    • affected V500R001C20SPC300PWE
    • affected V500R001C30
    • affected V500R001C30SPC100
    • affected V500R001C30SPC100PWE
    • affected V500R001C30SPC200
    • affected V500R001C30SPC200PWE
    • affected V500R001C30SPC300
    • affected V500R001C50
    • affected V500R001C50PWE
    • affected V500R001C80
    • affected V500R005C00
    • affected V500R001C00SPC500PWE
    • affected V500R002C00
    • affected V500R002C00SPC100
    • affected V500R002C00SPC100PWE
    • affected V500R002C00SPC200
    • affected V500R002C00SPC200PWE
    • affected V500R002C00SPC300
    • affected V500R002C10
    • affected V500R002C10PWE
    • affected V500R002C30
    • and 47 more

References

References1

Sources

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

Badge for a README or a ticket

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

Record last updated .