Skip to main content
CVE-2023-47035VulnerabilityPublished Updated

CVE-2023-47035: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

Given the lack of vendor or product specifics, mitigation should focus on general best practices tailored to the vulnerability's nature: 1) Implement strict validation and status checks on critical parameters controlling transfer operations, such as 'tradingOpen', ensuring that operations cannot proceed unless explicitly authorized. 2) Employ network-level protections such as firewalls and intrusion detection/prevention systems to monitor and restrict unauthorized access attempts to transfer-related services. 3) Enforce robust logging and monitoring of transfer operations to detect anomalies or unauthorized activities promptly. 4) Apply principle of least privilege on services handling transfers to limit potential exploitation impact. 5) Conduct thorough code reviews and security testing focusing on parameter validation and access control logic. 6) Stay alert for vendor advisories or patches related to RPTC 0x3b08c or similar components and apply updates promptly once available. 7) Consider implementing multi-factor authentication and transaction verification mechanisms where applicable to add layers of security beyond parameter checks.

Description

RPTC 0x3b08c was discovered to not conduct status checks on the parameter tradingOpen. This vulnerability can allow attackers to conduct unauthorized transfer operations.

References

Community reviews

Loading reviews…