CVE-2020-11127: u'Integer overflow can cause a buffer overflow due to lack of table length check in the extensible boot Loader during the validation of…
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
u'Integer overflow can cause a buffer overflow due to lack of table length check in the extensible boot Loader during the validation of security metadata while processing objects to be loaded' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in MDM9205, QCM4290, QCS405, QCS410, QCS4290, QCS610, QSM8250, SA415M, SA515M, SA6145P, SA6150P, SA6155, SA6155P, SA8150P, SA8155, SA8155P, SA8195P, SC7180, SC8180X, SC8180X+SDX55, SC8180XP, SDA640, SDA845, SDA855, SDM1000, SDM640, SDM830, SDM845, SDM850, SDX24, SDX50M, SDX55, SDX55M, SM4125, SM4250, SM4250P, SM6115, SM6115P, SM6150, SM6150P, SM6250, SM6250P, SM6350, SM7125, SM7150, SM7150P, SM7225, SM7250, SM7250P, SM8150, SM8150P, SM8250, SXR2130, SXR2130P
- Published
- Nov 12, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-190
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| qualcomm | mdm9205 firmware | cpe:2.3:o:qualcomm:mdm9205_firmware |
| qualcomm | mdm9205 | cpe:2.3:h:qualcomm:mdm9205 |
| qualcomm | qcm4290 firmware | cpe:2.3:o:qualcomm:qcm4290_firmware |
| qualcomm | qcm4290 | cpe:2.3:h:qualcomm:qcm4290 |
| qualcomm | qcs405 firmware | cpe:2.3:o:qualcomm:qcs405_firmware |
| qualcomm | qcs405 | cpe:2.3:h:qualcomm:qcs405 |
| qualcomm | qcs410 firmware | cpe:2.3:o:qualcomm:qcs410_firmware |
| qualcomm | qcs410 | cpe:2.3:h:qualcomm:qcs410 |
| qualcomm | qcs4290 firmware | cpe:2.3:o:qualcomm:qcs4290_firmware |
| qualcomm | qcs4290 | cpe:2.3:h:qualcomm:qcs4290 |
| qualcomm | qcs610 firmware | cpe:2.3:o:qualcomm:qcs610_firmware |
| qualcomm | qcs610 | cpe:2.3:h:qualcomm:qcs610 |
and 94 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (qualcomm). Independent of NVD's CPE analysis and usually ahead of it.
Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking
- MDM9205, QCM4290, QCS405, QCS410, QCS4290, QCS610, QSM8250, SA415M, SA515M, SA6145P, SA6150P, SA6155, SA6155P, SA8150P, SA8155, SA8155P, SA8195P, SC7180, SC8180X, SC8180X+SDX55, SC8180XP, SDA640, SDA8affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm mdm9205 firmwareall versions
- qualcomm qcm4290 firmwareall versions
- qualcomm qcs405 firmwareall versions
- qualcomm qcs410 firmwareall versions
- qualcomm qcs4290 firmwareall versions
- qualcomm qcs610 firmwareall versions
- qualcomm qsm8250 firmwareall versions
- qualcomm sa415m firmwareall versions
- qualcomm sa515m firmwareall versions
- qualcomm sa6145p firmwareall versions
- qualcomm sa6150p firmwareall versions
- qualcomm sa6155 firmwareall versions
- qualcomm sa6155p firmwareall versions
- qualcomm sa8150p firmwareall versions
- qualcomm sa8155 firmwareall versions
- qualcomm sa8155p firmwareall versions
- qualcomm sa8195p firmwareall versions
- qualcomm sc7180 firmwareall versions
- qualcomm sc8180x firmwareall versions
- qualcomm sc8180xp firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-25745Always Incorrect Control Flow Implementation in MODEM39Monitor
- CVE-2019-10612UTCB object has a function pointer called by the reaper to deallocate its memory resources and this address can potentially be corrupted by…39Monitor
- CVE-2019-2294Usage of hard-coded magic number for calculating heap guard bytes can allow users to corrupt heap blocks without heap algorithm knowledge…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-2267Jan 21, 2020 · Locked regions may be modified through other interfaces in secure boot loader image due to improper access control.31Monitor
- ← EarlierCVE-2019-14030Mar 5, 2020 · The size of a buffer is determined by addition and multiplications operations that have the potential to overflow due to lack of bound…31Monitor
- Later →CVE-2022-25726Apr 13, 2023 · Buffer Over-read in MODEM30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.