A weakness was found in Encrypt Only boot mode in Zynq UltraScale+ devices.
A weakness was found in Encrypt Only boot mode in Zynq UltraScale+ devices. This could lead to an adversary being able to modify the control fields of the boot image leading to an incorrect secure boot behavior.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Sep 3, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-657
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| amd | zu11eg firmware | cpe:2.3:o:amd:zu11eg_firmware |
| amd | zu11eg | cpe:2.3:h:amd:zu11eg |
| amd | zu15eg firmware | cpe:2.3:o:amd:zu15eg_firmware |
| amd | zu15eg | cpe:2.3:h:amd:zu15eg |
| amd | zu17eg firmware | cpe:2.3:o:amd:zu17eg_firmware |
| amd | zu17eg | cpe:2.3:h:amd:zu17eg |
| amd | zu19eg firmware | cpe:2.3:o:amd:zu19eg_firmware |
| amd | zu19eg | cpe:2.3:h:amd:zu19eg |
| amd | zu1cg firmware | cpe:2.3:o:amd:zu1cg_firmware |
| amd | zu1cg | cpe:2.3:h:amd:zu1cg |
| amd | zu1eg firmware | cpe:2.3:o:amd:zu1eg_firmware |
| amd | zu1eg | cpe:2.3:h:amd:zu1eg |
and 70 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd zu11eg firmwareall versions
- amd zu15eg firmwareall versions
- amd zu17eg firmwareall versions
- amd zu19eg firmwareall versions
- amd zu1cg firmwareall versions
- amd zu1eg firmwareall versions
- amd zu21dr firmwareall versions
- amd zu25dr firmwareall versions
- amd zu27dr firmwareall versions
- amd zu28dr firmwareall versions
- amd zu29dr firmwareall versions
- amd zu2cg firmwareall versions
- amd zu2eg firmwareall versions
- amd zu39dr firmwareall versions
- amd zu3cg firmwareall versions
- amd zu3eg firmwareall versions
- amd zu3tcg firmwareall versions
- amd zu3teg firmwareall versions
- amd zu42dr firmwareall versions
- amd zu43dr firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.
n/a Zynq UltraScale+ SoC
- Not Fixedaffected
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-657 · Violation of Secure Design PrinciplesCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- github.com/inversepath/advisories/blob/master/Security_Advisory-Ref_FSC-HWSEC-VR2019-0001-Xilinx_ZU+-Encrypt_Only_Secure_Boot_bypass.txt
- www.xilinx.com/support/answers/72588.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.