CVE-2024-48645VulnerabilityPublished 21 Oct 2024

CVE-2024-48645: command-block-ide · n/a

Affects command-block-ideSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.5.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.5.0

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

Attack Complexity: Low
Attack Vector: Network
Availability: None
Confidentiality: None
Integrity: High
Privileges Required: None
Scope: Unchanged
User Interaction: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Availability: None: There is no impact to availability within the impacted component.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade arm32x/command-block-ide to 0.5.0.

Affected software

Product	Affected	Fixed in
GitHubarm32x/command-block-ide`pkg:github/arm32x/command-block-ide`Other threats	Affected <0.5.0	Fixed in 0.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict access to the server’s file system, ensuring only trusted administrators can modify function files. 2. Implement strict server-side permissions and access controls to prevent unauthorized users from uploading or editing files. 3. Monitor file integrity regularly using automated tools or scripts to detect unauthorized changes to function files. 4. Isolate the Minecraft server environment from other critical infrastructure to limit potential lateral movement if compromised. 5. Educate server administrators and users about the risks of installing untrusted mods and encourage the use of mods from reputable sources. 6. Keep an eye on official mod repositories and security advisories for patches or updates addressing this vulnerability and apply them promptly once available. 7. Consider temporarily disabling or removing the Command Block IDE mod until a secure version is released. 8. Use network-level protections such as firewalls and VPNs to limit access to the dedicated server to trusted users only.

Description

In Minecraft mod "Command Block IDE" up to and including version 0.4.9, a missing authorization (CWE-862) allows any user to modify "function" files used by the game when installed on a dedicated server.

Impact

The primary impact of CVE-2024-48645 is on the integrity of Minecraft dedicated servers running the vulnerable mod. Unauthorized modification of function files can allow attackers to alter game commands and logic, potentially disrupting gameplay, causing unfair advantages, or introducing malicious behaviors. This can degrade user experience, damage the reputation of server operators, and lead to loss of trust among players. In environments where Minecraft servers are used for educational or organizational purposes, such manipulation could undermine instructional activities or collaborative projects. Although confidentiality and availability are not directly affected, the integrity compromise could be leveraged as a foothold for further attacks or social engineering within the gaming community. The ease of exploitation and lack of authentication requirements increase the risk, especially for public or poorly secured servers.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 21:37 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats