potential buyers are discussing about a $1.2 trillion to $1.3 trillion valuation range for the company, according to people familiar with the matter. Some are weighing a value as low as $1.1 trillion
"An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network. Successful exploitation could allow the attacker to execute code on the target system. No authentication or user interaction is required.."
It mentions that it may rely on other services or security measures running- I wonder if there’s something like this hitting a firewall or av and then that calling out to paint to check file type or size out something like that?
But why MS Paint? What functionality does it offer to another program to get called on specifically? And if this other service isn't calling on it specifically, what else can it be tricked into calling? And how many of those are also vulnerable to being stabbed in the back? The smaller interior holes are a problem, sure, but it seems like the CVE should be for the hull hole in that case.
Sounds like they just mean opening a file that you got from somewhere else.
>The CVSS score of 8.1 marks this as a high‑severity RCE. The EPSS score is not available, and the vulnerability is not listed in CISA’s KEV catalog. Based on the description, the likely attack vector is remote: an attacker can deliver the malicious file over a network connection, for example via Remote Desktop, file shares, or other network‑exposed services that allow users to open images. The lack of EPSS data does not diminish the threat posed by a known RCE, but it does make precise likelihood estimation difficult.
> After applying the update, verify that the target Windows systems are running a version that includes the CVE fix before disabling legacy file‑open processing in Paint.
Which is complete nonsense. "Legacy file-open processing" isn't a real configurable option in Paint and this seems to suggest that enabling it is some sort of mitigation. The resolution is simply to update Paint.
The direct implication is that current generations of ms paint are a “service over the network.” Probably a theoretically possible RPC end point of svchost.exe
I'm thankfully out of the loop on Windows these days, but as I remember it Paint did not have any network features? Is that still true? If if is, maybe it is a misfiling of the CVE and it isn't remote?
Or are they chaining a browser auto opening a download in paint, (but browsers shouldn't do that)...
Why for the love of everything that is good does MS Paint have network trash in it. It's a super simple bitmap editor. Like Notepad, it's simple and just works.
Make a new product and bundle that as an option if you want to drastically change the functionality.
> Notepad in Windows includes AI features powered by Copilot that help refine and shorten text with the assistance of GPT. By default, these AI features are enabled on managed devices
I wonder if it could be through a file:// or some deeplink custom url handler that opens in Paint and clicking on it with some carefully crafted file path could make it read out of bounds (since that's the associated weakness reported) and execute something.
Whatever it is, it doesn't require any clicking or user interaction. Maybe my imagination is just limited but I can't imagine why Paint is making itself available for incoming traffic on the network.
Mine doesn't have a mouse or keyboard at the moment, so I'm only checking over an SSH->WSL connection. But it sure doesn't look like it's opening any ports from here.
So I guess either some random OS component is listening to the network and just-as-inexplicably asking Paint to do something for it. Or one of Paint's outbound connections is vulnerable if hijacked by a mitm. Network interception's one of the examples used for the "High" Attack Complexity rating that MS gave this CVE. Maybe powered by eMudhra for any systems that haven't revoked those certs? That'd be topical.
But still wouldn't really make sense. A patch for machines that are actively updating Paint but dodging cert revocations? Nothing really makes sense about this silly Paint CVE.
Or maybe after the .bmp file is executed, it can install something that opens an outbound TCP connection to its C2, and thus can receive commands. Would not need admin privileges because it doesn't open a port, just 'outbound' connections, like a long-poll.
you are right, it seems like the latter outbouns tcp connection is already being opened by paint, and that is what is exploitable.
since it exposes no port, I’d assume it isn’t trivial to exploit, paint will chose its target (a microsoft domain or IP), the exploit must involve some error in destination selection, or simply allowing a mitm to impersonate microsoft.
this is inline with Attack Complexity High, attacker needs to be either in the network path (mitm) or control the erroneous destination of the connection (say mircosoft.com), possibly blocking (dosing) the higher priority genuine destination
Seems odd even for a vibecoded copilot integration to make repeated, unprompted network requests. And if they're not repeated and unprompted, then we don't meet the "no user input" requirement.
Because the definition of "remote" has been expanded in the name of resume-driven development to include sending a malicious file that a victim has to open.
Cool! Have you also tried setting maximum display size in accessibility settings on android? I lost most of them at the stairs and the rest fell into the walls. Is that supposed to happen? None reached the bottom. That said, this is pretty cool.
Companies who care about whether their FIPS implementation is validated or not would probably prefer buying from a company who sells it over relying on a guy at their company to get cmake back on track regularly. At that point, it's not just about the module, it's about custody, liability, etc.
Jeez laweez. Since when can lawyers make good technical decisions?
I saw a PIN terminal reboot a while ago and the openSSL version was ancient, pretty much historic at that point. But it has an unbroken seal on it, so it's safe, right?
It isn't just compiling something that works. You need to compile it exactly as specified. And document the entire process so you can prove to an auditor that you did everything correctly. Oh, and there's a list of tested platforms, and if your platform isn't on there, which Debian probably isn't, you need to explain to the auditor why it's ok, and why it isn't reasonable for you to use one of the platforms it was tested on.
What you are paying for is not saving the time of a developer compiling something. It's reducing the friction when you go through an audit.
I wonder what the specifics of certification are. No certificate can ever prove a given binary works correctly. No one really understands how computers work, but here's a piece of paper that says Oracle Linux 11.0 is okay. It was expensive and it has a seal of approval on it, so that proves it.
The good thing was a LOT of bugs were fixed in those 2 months. Also you can install or upgrade to U+1, so you could've upgraded in april.
reply