CVE-2022-26157
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 issue was discovered in the web application in Cherwell Service Management (CSM) 10.2.3. The ASP.NET_Sessionid cookie is not protected by the Secure flag. This makes it prone to interception by an attacker if traffic is sent over unencrypted channels.
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 confidenceThe ASP.NET_Sessionid cookie in Cherwell Service Management 10.2.3 is missing the Secure flag, allowing it to be transmitted over unencrypted HTTP connections. An attacker on the same network could intercept the session cookie and perform session hijacking attacks.
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= 10.2.3CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify installed Cherwell versionCheck the installed version of Cherwell Service Management. This is typically accessible through the Cherwell Administration console under System Setup > General Settings, or by viewing the application in Windows Programs and Features.Affected if Version is 10.2.3 (other versions are not affected by this specific CVE)
-
Capture HTTP response cookieSend an HTTP (not HTTPS) request to the Cherwell login page or any authenticated endpoint. Use browser developer tools (Network tab) or a web proxy to capture the response headers. Locate the Set-Cookie header for ASP.NET_Sessionid.Affected if The ASP.NET_Sessionid cookie is present without the Secure attribute in the Set-Cookie header over HTTP
-
Inspect web.config cookie configurationNavigate to the Cherwell web.config file in the installation directory (commonly in the web root or inetpub folder). Open the file and locate the <httpCookies> element within the <system.web> section. Check the requireSSL attribute setting.Affected if requireSSL is set to false or the httpCookies element is missing or lacks the requireSSL attribute
The environment is affected if running Cherwell Service Management version 10.2.3 and the ASP.NET_Sessionid cookie is served without the Secure flag, which can be confirmed by inspecting HTTP response headers or the web.config file.
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 dataConfigure the application to set the Secure flag on the ASP.NET_Sessionid cookie, ensuring it is only transmitted over HTTPS connections. This is typically done in the web.config file or through IIS cookie settings.
- Consultation1.0 h
- Implementation1.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-2022-26157 — 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-26157 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