CVE-2018-16552: Django crm MicroPyramid Django-CRM CSRF Vulnerability

HIGH
Advisory Identifier: GHSA-hq4r-47qc-3jhc
CVSS 8.8
CWE-352
Published
Advisory Summary

CVE-2018-16552 is a HIGH (CVSS 8.8) micropyramid django-crm csrf vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting Django crm libraries in the PyPI ecosystem. The issue involves micropyramid django-crm csrf. Remediation is available in the latest vendor maintenance releases.

CVE-2018-16552 at a Glance

CVE Identifier CVE-2018-16552
GHSA Identifier GHSA-hq4r-47qc-3jhc
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-352: Cross-Site Request Forgery (CSRF)
Affected Product Django crm
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2018-16552

To remediate this vulnerability, upgrade all affected Django crm dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

django-crm fixed: Latest secure release
pip install django-crm>=Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show django-crm

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2018-16552, inspect your installed packages using pip:

pip show django-crm

Analyze the terminal output to locate any version of Django crm in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The pip show django-crm command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-352: Cross-Site Request Forgery (CSRF), where the web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. In Django crm, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

MicroPyramid Django-CRM 0.2 allows CSRF for `/users/create/`, `/users/##/edit/`, and `/accounts/##/delete/` URIs.

CVE-2018-16552 Affected Django crm Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
django-crm
PyPI
≤ 0.2

References

Frequently Asked Questions

What is CVE-2018-16552?
CVE-2018-16552 is a security vulnerability in Django crm involving MicroPyramid Django-CRM CSRF under CWE-352: Cross-Site Request Forgery (CSRF).
Which Django crm versions are affected?
Affected versions include releases prior to current release patches across affected packages: django-crm.
What version fixes CVE-2018-16552?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is django-crm affected?
Yes, django-crm is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2018-16552?
CVE-2018-16552 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2018-16552?
CVE-2018-16552 is classified under CWE-352: Cross-Site Request Forgery (CSRF) (The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.).
How can I check PyPI dependencies for CVE-2018-16552?
Run the dependency tree command: 'pip show django-crm'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hq4r-47qc-3jhc",
  "modified" : "2024-09-16T21:25:32Z",
  "published" : "2022-05-13T01:11:25Z",
  "aliases" : [ "CVE-2018-16552" ],
  "summary" : "MicroPyramid Django-CRM CSRF",
  "details" : "MicroPyramid Django-CRM 0.2 allows CSRF for `/users/create/`, `/users/##/edit/`, and `/accounts/##/delete/` URIs.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "django-crm"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2018-16552"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/MicroPyramid/Django-CRM/issues/68"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/MicroPyramid/Django-CRM"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/django-crm/PYSEC-2018-65.yaml"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-352" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-07-20T18:58:58Z",
    "nvd_published_at" : "2018-09-05T22:29:00Z"
  }
}