CVE-2008-1396: Plone credentials stored in session cookie

plone Updated 02 Oct 2025

Summary

01/05/2022
No i
Moderate
Not published

CVE-2008-1396: Plone credentials stored in session cookie. Affects plone versions < 3.1.7. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Plone is a content management system (CMS) written in Python and is widely used for building websites and web applications. It provides a user-friendly interface for managing content and offers various features for customization and extensibility. However, Plone CMS 3.1.x is vulnerable to a security issue where credentials are stored in a session cookie. This vulnerability can be exploited by remote attackers to gain permanent access to an account by sniffing the network.

Vulnerability Detail

The vulnerability in Plone CMS 3.1.x arises from the use of invariant data (a client username and a server secret) when calculating an HMAC-SHA1 value for an authentication cookie. This makes it easier for attackers to intercept the network traffic and extract the credentials from the session cookie. By gaining access to the account, the attacker can potentially perform unauthorized actions and compromise the security of the system.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, it is advisable to use secure network protocols such as HTTPS to encrypt the network traffic and prevent interception of the session cookie. Additionally, implementing strong access controls and regularly monitoring the system for any suspicious activity can help mitigate the risk associated with this vulnerability.

Conclusion

In conclusion, the Plone CMS 3.1.x version is vulnerable to a security issue where credentials are stored in a session cookie. This can be exploited by remote attackers to gain unauthorized access to user accounts. It is crucial to upgrade to a patched version of Plone CMS and implement additional security measures to protect against this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for plone →

Share this vulnerability

FAQ

Plone CMS is a popular content management system written in Python, known for its user-friendly interface and extensibility.

The vulnerability allows remote attackers to gain permanent access to an account by sniffing the network, potentially leading to unauthorized actions and compromise of the system's security.

To fix this vulnerability, it is recommended to upgrade to a newer version of Plone CMS that includes the necessary security patches.

As a temporary workaround, using secure network protocols like HTTPS and implementing strong access controls can help mitigate the risk.

You can find more information about this vulnerability in the official advisory published by the Plone CMS developers.

Related vulnerabilities

Recent vulnerabilities recorded for plone.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback