Security readout for executives and security teams
Plain-English summary
CVE-2025-51677 describes a mismatch between the intended OR1200 CPU RTL and a synthesized netlist at an output port. Hardware built from the affected design could behave differently than expected, creating integrity and availability risk. Public data does not identify packaged products, deployed devices, or a vendor patch.
Executive priority
Treat as high priority only if your organization uses OR1200-derived hardware IP. For most software-only environments, immediate exposure is likely low, but hardware teams should verify provenance promptly.
Technical view
The record ties the issue to openRISC OR1200 commit 83ac6b and reports an RTL-versus-netlist output mismatch. The CVSS 3.1 score is 9.1, with high integrity and availability impact and no confidentiality impact. Affected CPEs and versions are listed as n/a, so exposure must be assessed from design provenance.
Likely exposure
Likely exposure is limited to organizations using, evaluating, or deriving hardware from OR1200 commit 83ac6b or related generated netlists. Evidence does not show broad consumer software exposure or named downstream products.
Exploitation context
The bundle reports KEV as false and provides no cited evidence of active exploitation. The risk is design-level: a mismatch may cause incorrect CPU output behavior after synthesis, which can affect system correctness or reliability.
Researcher notes
Public evidence is thin: the record names a commit and mismatch class but not a fixed version, exploit path, or affected products. Avoid assuming internet exploitability despite the CVSS vector; validate against hardware design flows and upstream issue details.
Mitigation direction
- Check upstream OpenRISC issue and CVE pages for vendor guidance or corrected commits.
- Inventory FPGA, ASIC, and verification projects using OR1200 commit 83ac6b.
- Avoid promoting affected netlists into production until equivalence is verified.
- Run RTL-to-netlist equivalence and regression checks for OR1200 output behavior.
- Document any downstream products or builds derived from the affected commit.
Validation and detection
- Confirm whether OR1200 commit 83ac6b exists in your hardware source history.
- Compare synthesized netlists against trusted RTL for relevant CPU output ports.
- Review synthesis logs and verification artifacts for output mismatch evidence.
- Check whether downstream forks incorporated fixes after the referenced issue.
- Track CVE record updates for clarified affected versions or remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-116: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-51677 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H3.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/openrisc/mor1kx/issues/160#issuecomment-2585618940CVE reference, mitre
- https://www.arxiv.org/abs/2504.18812CVE reference, mitre
- https://mason.gmu.edu/~rsaravan/projects/synfuzz/cve/cve.htmlCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Encoding or Escaping of Output
Improper Encoding or Escaping of Output represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.