CVE-2012-0328
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 · uneditedJanetter before 3.3.0.0 (aka 3.3.0) allows remote attackers to obtain session information for twitter.com web sites via unspecified vectors.
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 · moderate confidenceJanetter Twitter client versions prior to 3.3.0.0 contain a vulnerability allowing remote attackers to obtain session information for twitter.com. The exact attack vector is not specified in the available documentation, but the flaw appears to involve improper handling or protection of session data, potentially enabling session hijacking or credential theft.
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<= 3.2.1.1= 1.0.0.0= 1.1.0.0= 1.2.0.0= 1.2.1.0= 1.3.0.0= 1.4.0.0= 1.5.0.0= 1.6.0.0= 1.6.1.0= 1.6.2.0= 1.6.3.0CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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.
-
Locate Janetter installationSearch for Janetter in the system: check Program Files (Windows) or Applications folder (Mac) for a folder named 'Janetter' or files with 'janetter' in the name. Also check Start Menu or Launchpad for Janetter shortcuts.Affected if Janetter is found installed on the system
-
Determine installed versionOpen Janetter and navigate to Help > About (or equivalent menu item). The version number will be displayed in the About dialog window.Affected if The displayed version is 3.2.1.1 or lower, OR is one of these: 1.0.0.0, 1.1.0.0, 1.2.0.0, 1.2.1.0, 1.3.0.0, 1.4.0.0, 1.5.0.0, 1.6.0.0, 1.6.1.0, 1.6.2.0, or 1.6.3.0
-
Check recent usage of the clientReview recent activity logs, browser history, or the Janetter application itself to see if the client has been used to connect to Twitter accounts.Affected if The vulnerable version is installed AND the client has been used to access Twitter, meaning session data may have been exposed
If Janetter version is 3.2.1.1 or lower, or any of versions 1.0.0.0 through 1.6.3.0, and the client has been used to access Twitter, the environment is likely affected by this session information disclosure vulnerability.
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 dataUsers should update Janetter to version 3.3.0.0 or later. Until updated, avoid using the vulnerable client version to access Twitter and consider using the official Twitter web interface or alternative trusted clients.
- Consultation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0328 — 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-2012-0328 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