Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Microsoft Security Windows IT Technology

Microsoft Obliquely Acknowledges Windows 0-day Bug Published on Twitter (arstechnica.com) 66

A privilege escalation flaw in Windows 10 was disclosed earlier this week on Twitter. From a report: The flaw allows anyone with the ability to run code on a system to elevate their privileges to "SYSTEM" level, the level used by most parts of the operating system and the nearest thing that Windows has to an all-powerful superuser. This kind of privilege escalation flaw enables attackers to break out of sandboxes and unprivileged user accounts so they can more thoroughly compromise the operating system. Microsoft has not exactly acknowledged the flaw exists; instead it offered a vague and generic statement: "Windows has a customer commitment to investigate reported security issues, and proactively update impacted devices as soon as possible. Our standard policy is to provide solutions via our current Update Tuesday schedule." So, if the flaw is acknowledged (and it's certainly real!) then the company will most likely fix it in a regular update released on the second Tuesday of each month.
This discussion has been archived. No new comments can be posted.

Microsoft Obliquely Acknowledges Windows 0-day Bug Published on Twitter

Comments Filter:
  • by Geoffrey.landis ( 926948 ) on Wednesday August 29, 2018 @02:48PM (#57219828) Homepage

    Unless there's more than is in the summary, the headline should read "Microsoft does not Acknowledge Windows 0-day Bug Published on Twitter".

  • by Anonymous Coward

    I mean, if we're going to spin words here...

  • by guruevi ( 827432 ) on Wednesday August 29, 2018 @03:40PM (#57220246)

    If you see the comments and write up in the documents and demo he released. It's fairly easy to exploit, in lay terms: the Task Scheduler read/writes to a location as SYSTEM and you can ask it to write any permissions to that file. Since the location of that file is publicly accessible for everyone, you could replace a job file with a DLL and then the system will write permissions for it to be executable as SYSTEM.

    • Windows 10 will soon force monthly charges. [slashdot.org]

      Basically, if there is a monthly charge for Windows 10, Microsoft will make more money if there are more bugs in updates. They will apparently fix the bugs only for those who are paying monthly.
      • Re: (Score:3, Interesting)

        by Desler ( 1608317 )

        The Microsoft Managed Desktop which is what those articles discuss willnot be forced on to anyone and are specifically being targeted to business users. Nowhere in the Mary Jo Foley article does it say that anyone will be forced into the service. What your spreading is actual fake news.

      • by jezwel ( 2451108 )

        Basically, if there is a monthly charge for Windows 10, Microsoft will make more money if there are more bugs in updates. They will apparently fix the bugs only for those who are paying monthly.

        I find this interesting as essentially this is what most companies already do with software, though on a different scale - annual maintenance charges that provide bug-fixes and updates. Many are moving to monthly fees so that the user has "more flexibility" around how much of a service they want to consume.
        Oops, your monthly charge is usually a fair bit more than an annual charge divided by 12 months. You've got all that extra flexibility remember?
        Anyone need full time access? Coincidentally your month

    • by Anonymous Coward

      This is /. so you don't have to oversimplify.
      What's actually going on is that the task scheduler has an API that allows you to set the DACL (discretionary access control list, the list of permissions for various user accounts or groups) for a task's folder and .job file in the Tasks folder. Since the task scheduler runs under the system account, it should impersonate the caller when doing so, since otherwise when setting the permissions, the kernel will check if system, rather than the caller, is allowed to

Programmers do it bit by bit.

Working...