CVE-2022-32778
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn information disclosure vulnerability exists in the cookie functionality of WWBN AVideo 11.6 and dev master commit 3f7c0364. The session cookie and the pass cookie miss the HttpOnly flag, making them accessible via JavaScript. The session cookie also misses the secure flag, which allows the session cookie to be leaked over non-HTTPS connections. This could allow an attacker to steal the session cookie via crafted HTTP requests.This vulnerability is for the pass cookie, which contains the hashed password and can be leaked via JavaScript.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn WWBN AVideo 11.6 and dev master, the session cookie and pass cookie are missing the HttpOnly flag, allowing them to be accessed via JavaScript through XSS. Additionally, the session cookie lacks the secure flag, enabling leakage over non-HTTPS connections. The pass cookie contains the hashed password, providing attackers with credential material.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 11.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed AVideo versionLocate the version file or admin panel in your AVideo installation. Common paths include view/info.php or checking the dashboard for version information. Compare the version number to 11.6.Affected if The installed version is exactly 11.6 or falls within the 11.6 release line.
-
Inspect session cookie for HttpOnly flagLog into your AVideo application and use browser DevTools (Application tab > Cookies) or capture the HTTP response headers on login. Examine the session cookie (often named PHPSESSID, session, or similar) for the HttpOnly attribute.Affected if The session cookie does not have the HttpOnly flag set.
-
Inspect pass cookie for HttpOnly flagAfter authentication, examine all cookies set by the application. Look for a cookie named 'pass', 'password', or similar that contains the hashed password value. Check whether this cookie has the HttpOnly attribute.Affected if A pass cookie exists and it lacks the HttpOnly flag.
-
Inspect session cookie for Secure flagExamine the session cookie in browser DevTools or HTTP headers to verify if the Secure attribute is present, which restricts transmission to HTTPS only.Affected if The session cookie does not have the Secure flag set.
You are affected if running AVideo 11.6 and any of the session or pass cookies are missing HttpOnly, or the session cookie is missing the Secure flag.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSet the HttpOnly and Secure flags on both session and pass cookies in the application's cookie configuration. This prevents JavaScript access and ensures cookies are only transmitted over encrypted HTTPS connections.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32778 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-32778 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data