CVE-2024-34517: Medium severity neo4j neo4j community vulnerability
Published May 7, 2024
·Updated
The Cypher component in Neo4j 5.0.0 through 5.18 mishandles IMMUTABLE privileges in some situations where an attacker already has admin access.
Other sources
The Cypher component in Neo4j between v.5.0.0 and v.5.19.0 mishandles IMMUTABLE.
— GitHub
Affected Software
2 affected componentsFixes available
maven/org.neo4j:neo4j-cypher>=5.0.0<5.19.0
5.19.0
Neo4j Neo4j Community>=5.0.0<5.19.0
Event History
May 7, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·06:30 PM
Frequently Asked Questions
1
What is the severity of CVE-2024-34517?
CVE-2024-34517 is classified as a high severity vulnerability due to its potential impact on system integrity.
2
How do I fix CVE-2024-34517?
To fix CVE-2024-34517, upgrade the Neo4j Cypher component to version 5.19.0 or later.
3
What versions of Neo4j are affected by CVE-2024-34517?
CVE-2024-34517 affects Neo4j versions between 5.0.0 and 5.19.0 inclusive.
4
What component is impacted by CVE-2024-34517?
CVE-2024-34517 impacts the Cypher component within the Neo4j database system.
5
Is there a workaround for CVE-2024-34517?
There is no documented workaround for CVE-2024-34517; upgrading to the patched version is recommended.