LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35621: Access control vulnerability in Evoh NFT EvohClaimable contract with sha256 hash code fa2084d5abca91a62ed1d...

Access control vulnerability in Evoh NFT EvohClaimable contract with sha256 hash code fa2084d5abca91a62ed1d2f1cad3ec318e6a9a2d7f1510a00d898737b05f48ae allows remote attackers to execute fraudulent NFT transfers.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE describes an access control flaw in an Evoh NFT EvohClaimable smart contract. The reported impact is fraudulent NFT transfers, meaning ownership or transfer integrity may be affected. The sources do not identify a vendor, affected product version, patch, or active exploitation.

Executive priority

Treat this as a targeted Web3 asset-integrity issue, not a broad enterprise software emergency. Prioritize action if the organization owns, custodies, sells, or depends on Evoh NFT assets connected to the referenced contract.

Technical view

CVE-2022-35621 is mapped to CWE-284 and CVSS 3.1 score 5.3. The vector is network-accessible, low complexity, no privileges, no user interaction, with low integrity impact only. The vulnerable artifact is identified by a SHA-256 contract hash, but affected product metadata is listed as n/a.

Likely exposure

Exposure appears limited to parties using or relying on the referenced Evoh NFT EvohClaimable contract or assets transferred through it. The bundle does not provide chain, address, deployment, vendor, or version details, so asset-specific verification is required.

Exploitation context

The CVE says remote attackers can execute fraudulent NFT transfers. However, KEV is false, and the provided sources do not confirm active exploitation, exploit maturity, affected deployments, or remediation status.

Researcher notes

Evidence is sparse. Affected vendor, product, versions, chain, address, and fix are not provided in the bundle. Anchor analysis to the exact hash and public reference, and avoid extrapolating to unrelated NFT contracts without confirmation.

Mitigation direction

  • Check the referenced project or vendor guidance for any migration or replacement instructions.
  • Pause business reliance on NFTs tied to the affected contract until ownership integrity is verified.
  • Review marketplace, wallet, and custody controls for assets associated with the contract.
  • Monitor the CVE record and GitHub reference for remediation updates.
  • Preserve transaction evidence if suspicious transfers are identified.

Validation and detection

  • Inventory Web3 assets for links to the referenced EvohClaimable contract hash.
  • Verify whether organizational wallets interacted with the affected contract.
  • Review ownership and transfer history for unexpected NFT movements.
  • Confirm whether any marketplace listings depend on disputed asset ownership.
  • Track CVE and repository updates for clarified affected deployments or fixes.
Prepared
Confidence
medium
Sources
3

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.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookup
cve · low confidence lookup

CVE-2022-35621 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
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
2Source 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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2022-35621Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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

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

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.