On 3/5/2026 9:47 AM, Waldek Hebisch wrote:
Simon Clubley <clubley@remove_me.eisner.decus.org-earth.ufp> wrote:
I would recommend people ask VSI if this is actually something that
can be made to be an outright vulnerability. _If_ it is, VSI really,
really, need to update this description to draw attention to this and
to also issue a CVE.
_IF_ this is a vulnerability, then the kind of language used in that CVE >>> description is also the same kind of language that needs to be used
here.
Deciding if this is vulnerability or not may be tricky and I VSI
may prefer to spend resources on fixing this.-a IIUC CVE is issued
when there is some plausible way to exploit it.-a AFAIK several things
first deemed impossible to exploit turned out to be vulnerabilities.
So P1 looks reasonable and if there are no known exploit then not
issuing CVE is reasonable too.
To put it differently, "mere process crasher" is IMO rather rare.
Usualy it is potential vulnerability.
Yes.
Everything related to DCL and data in P1 space above the start
of the user mode stack is sensitive, because it is privileged
stuff.
I think the bottom line is: PATCH NOW!
Arne
On 3/5/2026 8:57 AM, Arne Vajh|+j wrote:
Everything related to DCL and data in P1 space above the start
of the user mode stack is sensitive, because it is privileged
stuff.
I think the bottom line is: PATCH NOW!
I assume that there is not a patch for all platforms, all versions?
What are the names of the files that are affected?
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (1 / 5) |
| Uptime: | 34:51:47 |
| Calls: | 1,266 |
| Files: | 1,362 |
| D/L today: |
3 files (6,742K bytes) |
| Messages: | 284,655 |