Snyk Security Database

screenshot-desktop is a malicious package. This package contains malicious code, and its content was removed from the official package manager. While this package might be attempting to impersonate a valid organization, there is no connection between that organization and this package authorship.

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the SpatialReference class in django/contrib/gis/gdal/srs.py, reached through GEOSGeometry.transform(), OGRGeometry.transform(), GDALRaster.transform(), and the srs and srid setters of OGRGeometry and GDALRaster. An attacker can make the server issue outbound file and network requests, and by observing those requests infer local file contents, by supplying an untrusted spatial-reference string that GDAL's OSRSetFromUserInput resolves as an external reference. Exploitation requires an application that passes untrusted input into GeoDjango's spatial-reference handling, and the external resolution is a default of the underlying GDAL library.

Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information in the CacheInterceptor class, whose shared cache key carries no per-user marker and which decides to store a response in the client level shared tier from Cache-Control and Expires alone. An attacker can read another user's response body by requesting the same URL through a CachingWebClient that serves multiple principals, since a response to a request carrying an Authorization header is stored in the shared tier even though max-age alone does not make it shareable, after which a session private miss falls back to that tier and an anonymous request receives the stored body in place of the origin's 401. Where the stored response carries Set-Cookie, the cookie is replayed verbatim to later callers, handing one user's session identifier to another and enabling session fixation or hijacking. Both cases require a single CachingWebClient shared across user principals, which is the documented pattern of a per-user WebClientSession layered over a shared caching client, together with an origin that marks the response cacheable without private or no-store.