Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-x3cv-r3g3-fpg9
No affected components available
Summary
The read_only mode in mcp-neo4j-cypher versions prior to 0.6.0 can be bypassed using CALL procedures.
Details
Impact
The enforcing of read_only mode in vulnerable versions could be bypassed by certain APOC procedures.
Patches
v0.6.0 release hardened the checks around the mode. The only way to guarantee the server actions is to limit the permissions of the db credentials available to the server.
Notes
Impacts for server-side request forgery vulnerabilities may depend on both the configuration of the vulnerable system as well as the presence of other systems in the environment that could be accessed as part of exploitation.
Recommended hardening
- Limit the apoc procedures to what's required
- Manage data loading privileges
- Don't relax the default settings without compensating controls
apoc.import.file.enabledisfalseby defaultapoc.import.file.use_neo4j_configistrueby default to restrict file imports to the import folder
Credits
We want to publicly recognise the contribution of Yotam Perkal from Pluto Security.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability.
Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard