LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41613: An issue was discovered in the controller unit of the OpenRISC mor1kx processor.

An issue was discovered in the controller unit of the OpenRISC mor1kx processor. The write logic of Exception Effective Address Register (EEAR) is not implemented correctly. User programs from authorized privilege levels will be unable to write to EEAR.

MediumCVSS 4.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-41613 is a logic flaw in the OpenRISC mor1kx processor controller. Authorized user programs may be unable to write the Exception Effective Address Register, causing incorrect processor behavior. Business urgency is moderate and mainly relevant to products, FPGA/SoC designs, or research systems that embed mor1kx.

Executive priority

Prioritize inventory and dependency confirmation over emergency response. This is a medium-severity processor logic issue with unclear affected versions and no cited active exploitation, but it can matter where mor1kx underpins deployed hardware or firmware behavior.

Technical view

The issue affects the controller unit write logic for EEAR in OpenRISC mor1kx. The CVSS 3.1 score is 4.3, with low complexity and required low privileges, impacting integrity only. The source bundle does not identify affected versions, CPEs, a patch, or vendor mitigation.

Likely exposure

Exposure appears limited to systems or designs using the OpenRISC mor1kx processor. The source bundle lists affected vendor, product, and versions as n/a, so exact vulnerable releases and downstream deployments cannot be confirmed from the supplied evidence.

Exploitation context

The source bundle and KEV status do not support active exploitation. The described condition requires authorized privilege level access and relates to incorrect EEAR write behavior, not unauthenticated compromise. No weaponized exploit or public attack activity is cited.

Researcher notes

Evidence is sparse: CVE metadata names the flawed EEAR write logic but does not provide affected versions, CWE, patch status, or downstream product mapping. Treat findings as provisional and validate against upstream mor1kx issue data and local RTL revision history.

Mitigation direction

  • Inventory products, FPGA designs, firmware, and research platforms for mor1kx usage.
  • Check upstream mor1kx and CVE sources for confirmed fixes or workarounds.
  • Review vendor or project guidance before changing processor RTL or downstream builds.
  • Limit reliance on affected EEAR behavior until validation is complete.

Validation and detection

  • Confirm whether any deployed component includes OpenRISC mor1kx.
  • Identify the exact mor1kx revision used in each affected design.
  • Review tests for EEAR write behavior from authorized privilege levels.
  • Track the GitHub issue and CVE record for updated affected-version data.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2021-41613 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2021-41613Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.