CVE-2011-4952: CSRF
Published Nov 19, 2019
·Updated
cobbler: Web interface lacks CSRF protection when using Django framework
Affected Software
3 affected componentsFixes available
pip/cobbler<2.6.0
2.6.0
debian/cobbler
Cobblerd Cobbler
Event History
Nov 19, 2019
CVE Published
via MITRE·03:29 PM
Data Sourced
via MITRE·03:29 PM
DescriptionWeakness
Apr 22, 2022
Advisory Published
via GitHub·12:24 AM
Frequently Asked Questions
1
What is the severity of CVE-2011-4952?
CVE-2011-4952 is classified with a moderate severity due to the lack of Cross-Site Request Forgery (CSRF) protection in the Cobbler web interface.
2
How do I fix CVE-2011-4952?
To fix CVE-2011-4952, upgrade to Cobbler version 2.6.0 or higher, which includes CSRF protection.
3
Which versions are affected by CVE-2011-4952?
Versions of Cobbler below 2.6.0 are affected by CVE-2011-4952 and lack proper CSRF protection.
4
What systems are impacted by CVE-2011-4952?
CVE-2011-4952 impacts any systems running affected versions of the Cobbler web interface that use the Django framework.
5
Is additional security required if I upgrade from CVE-2011-4952?
While upgrading mitigates the CSRF vulnerability, it is still recommended to implement additional security measures such as input validation and user authentication.