Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.83% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2020
CVE-2020-9247High confidence
There is a buffer overflow vulnerability in several Huawei products
Huawei · HONOR 20 PRO
7.8HighCVSS 3.1
Within 7 days
Fix not verifiedHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Huawei HONOR 20 PRO and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Fix not verified01
What, why and how
There is a buffer overflow vulnerability in several Huawei products. The system does not sufficiently validate certain configuration parameter which is passed from user that would cause buffer overflow. The attacker should trick the user into installing and running a malicious application with a high privilege, successful exploit may cause code execution. Affected product include Huawei HONOR 20 PRO, Mate 20, Mate 20 Pro, Mate 20 X, P30, P30 Pro, Hima-L29C, Laya-AL00EP, Princeton-AL10B, Tony-AL00B, Yale-L61A, Yale-TL00B and YaleP-AL10B.
What
There is a buffer overflow vulnerability in several Huawei products. The system does not sufficiently validate certain configuration parameter which is passed from user that would cause buffer overflow. The attacker should trick the user into installing and running a malicious application with a high privilege, successful exploit may cause code execution. Affected product include Huawei HONOR 20 PRO, Mate 20, Mate 20 Pro, Mate 20 X, P30, P30 Pro, Hima-L29C, Laya-AL00EP, Princeton-AL10B, Tony-AL00B, Yale-L61A, Yale-TL00B and YaleP-AL10B.
Why
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
There is a buffer overflow vulnerability in several Huawei products. The system does not sufficiently validate certain configuration parameter which is passed from user that would cause buffer overflow. The attacker should trick the user into installing and running a malicious application with a high privilege, successful exploit may cause code execution. Affected product include Huawei HONOR 20 PRO, Mate 20, Mate 20 Pro, Mate 20 X, P30, P30 Pro, Hima-L29C, Laya-AL00EP, Princeton-AL10B, Tony-AL00B, Yale-L61A, Yale-TL00B and YaleP-AL10B.
Why
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-120 ↗
CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'). The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix not verified
- Affected
- HONOR 20 PRO: unspecified < 10.1.0.230(C432E9R5P1), unspecified < 10.1.0.231(C10E3R3P2)
- HUAWEI Mate 20: unspecified < 10.1.0.160(C00E160R3P8)
- HUAWEI Mate 20 Pro: unspecified < 10.1.0.270(C432E7R1P5), unspecified < 10.1.0.270(C635E3R1P5), unspecified < 10.1.0.273(C185E7R2P4), unspecified < 10.1.0.273(C636E7R2P4), unspecified < 10.1.0.277(C10E7R2P4), unspecified < 10.1.0.277(C605E7R1P5)
- HUAWEI Mate 20 X: unspecified < 10.1.0.160(C00E160R2P8)
- HUAWEI P30: 9.1.0.272(C635E4R2P2), unspecified < 10.1.0.123(C432E22R2P5), unspecified < 10.1.0.126(C10E7R5P1), unspecified < 10.1.0.126(C185E4R7P1), unspecified < 10.1.0.126(C605E19R1P3), unspecified < 10.1.0.126(C636E5R3P4), unspecified < 10.1.0.126(C636E7R3P4)
- HUAWEI P30 Pro: unspecified < 10.1.0.160(C00E160R2P8)
- Hima-L29C: unspecified < 10.1.0.273(C185E5R2P4), unspecified < 10.1.0.273(C636E5R2P4), unspecified < 10.1.0.275(C10E4R2P4)
- Laya-AL00EP: unspecified < 10.1.0.160(C786E160R3P8)
- Princeton-AL10B: unspecified < 10.1.0.160(C00E160R2P11)
- Tony-AL00B: unspecified < 10.1.0.160(C00E160R2P11)
- Yale-L61A: unspecified < 10.1.0.225(C432E3R1P2), unspecified < 10.1.0.226(C10E3R1P1)
- Yale-TL00B: unspecified < 10.1.0.160(C01E160R8P12)
- YaleP-AL10B: unspecified < 10.1.0.160(C00E160R8P12)
- Fixed
- No fixed version is explicitly recorded in the structured CVE data.
- Action
- No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 7 Dec 2020 · Last source change 4 Aug 2024, 10:19 UTC · CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2020-30076
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.