STE WILLIAMS

SEC Charges Former Equifax Exec with Insider Trading

CIO of a US business unit within Equifax had reportedly learned of the company’s data breach and sold his shares for nearly $1 million.

The Securities and Exchange Commission (SEC) has charged a former Equifax executive with insider trading ahead of the company’s disclosure of a massive data breach in Sept. 2017. Jun Ying, a former CIO within a US business unit of Equifax, was next in line to be its global CIO.

The SEC alleges Ying used confidential corporate information to determine Equifax had been breached. Before Equifax disclosed the incident, the SEC claims Ying exercised his vested Equifax stock options and sold his shares, collecting nearly $1 million. The SEC says by selling his shares ahead of the company’s announcement, he avoided more than $117,000 in losses.

“Corporate insiders who learn inside information, including information about material cyber intrusions, cannot betray shareholders for their own financial benefit,” says Richard Best, director of the SEC’s Atlanta Regional Office, in a statement. The SEC is charging Ying with violating the antifraud provisions of the federal securities laws.

This news follows updated guidance published by the SEC in Feb. 2018, that calls for public companies to give investors more intel on cybersecurity incidents and risks in a more timely fashion. The commission also states corporate officers, directors, and other insiders are not allowed to trade shares if they have unpublicized knowledge of a corporate security incident.

Read more details here.

Interop ITX 2018

Join Dark Reading LIVE for two cybersecurity summits at Interop ITX. Learn from the industry’s most knowledgeable IT security experts. Check out the security track here.

Dark Reading’s Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Article source: https://www.darkreading.com/attacks-breaches/sec-charges-former-equifax-exec-with-insider-trading/d/d-id/1331272?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

SEC Charges Former Equifax Exec with Insider Trading

CIO of a US business unit within Equifax had reportedly learned of the company’s data breach and sold his shares for nearly $1 million.

The Securities and Exchange Commission (SEC) has charged a former Equifax executive with insider trading ahead of the company’s disclosure of a massive data breach in Sept. 2017. Jun Ying, a former CIO within a US business unit of Equifax, was next in line to be its global CIO.

The SEC alleges Ying used confidential corporate information to determine Equifax had been breached. Before Equifax disclosed the incident, the SEC claims Ying exercised his vested Equifax stock options and sold his shares, collecting nearly $1 million. The SEC says by selling his shares ahead of the company’s announcement, he avoided more than $117,000 in losses.

“Corporate insiders who learn inside information, including information about material cyber intrusions, cannot betray shareholders for their own financial benefit,” says Richard Best, director of the SEC’s Atlanta Regional Office, in a statement. The SEC is charging Ying with violating the antifraud provisions of the federal securities laws.

This news follows updated guidance published by the SEC in Feb. 2018, that calls for public companies to give investors more intel on cybersecurity incidents and risks in a more timely fashion. The commission also states corporate officers, directors, and other insiders are not allowed to trade shares if they have unpublicized knowledge of a corporate security incident.

Read more details here.

Interop ITX 2018

Join Dark Reading LIVE for two cybersecurity summits at Interop ITX. Learn from the industry’s most knowledgeable IT security experts. Check out the security track here.

Dark Reading’s Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Article source: https://www.darkreading.com/attacks-breaches/sec-charges-former-equifax-exec-with-insider-trading/d/d-id/1331272?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

SEC Charges Former Equifax Exec with Insider Trading

CIO of a US business unit within Equifax had reportedly learned of the company’s data breach and sold his shares for nearly $1 million.

The Securities and Exchange Commission (SEC) has charged a former Equifax executive with insider trading ahead of the company’s disclosure of a massive data breach in Sept. 2017. Jun Ying, a former CIO within a US business unit of Equifax, was next in line to be its global CIO.

The SEC alleges Ying used confidential corporate information to determine Equifax had been breached. Before Equifax disclosed the incident, the SEC claims Ying exercised his vested Equifax stock options and sold his shares, collecting nearly $1 million. The SEC says by selling his shares ahead of the company’s announcement, he avoided more than $117,000 in losses.

“Corporate insiders who learn inside information, including information about material cyber intrusions, cannot betray shareholders for their own financial benefit,” says Richard Best, director of the SEC’s Atlanta Regional Office, in a statement. The SEC is charging Ying with violating the antifraud provisions of the federal securities laws.

This news follows updated guidance published by the SEC in Feb. 2018, that calls for public companies to give investors more intel on cybersecurity incidents and risks in a more timely fashion. The commission also states corporate officers, directors, and other insiders are not allowed to trade shares if they have unpublicized knowledge of a corporate security incident.

Read more details here.

Interop ITX 2018

Join Dark Reading LIVE for two cybersecurity summits at Interop ITX. Learn from the industry’s most knowledgeable IT security experts. Check out the security track here.

Dark Reading’s Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Article source: https://www.darkreading.com/attacks-breaches/sec-charges-former-equifax-exec-with-insider-trading/d/d-id/1331272?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Samba settings SNAFU lets any user change admin passwords

Samba admins: get patching and/or updating. Unless you’re content to have your admin passwords overwritten by, well, anyone else using Samba.

That’s the gist of an advisory warning that “On a Samba 4 Active Directory domain controller (AD DC) any authenticated user can change other users’ passwords over LDAP, including the passwords of administrative users and service accounts.”

“Samba vendors and administrators running affected versions are advised to upgrade or apply the patch as soon as possible,” the advisory adds.

The mess comes about because “… a Samba 4 AD DC the LDAP server in all versions of Samba from 4.0.0 onwards incorrectly validates permissions to modify passwords over LDAP allowing authenticated users to change any other users’ passwords, including administrative users and privileged service accounts (eg Domain Controllers).”

“The LDAP server incorrectly validates certain LDAP password modifications against the “Change Password” privilege, but then performs a password reset operation.”

There’s some good news in the form of this simple workaround samba_CVE-2018-1057_helper --lock-pwchange that turns off the mistakenly-loose password-setting permissions. Once you’ve done that, visit samba.org/samba/security/ to download patched Samba versions 4.7.6, 4.6.14 and 4.5.16 to fix recent releases. Older versions of the software may have patches here. ®

Sponsored:
Minds Mastering Machines – Call for papers now open

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2018/03/14/samba_password_bug/

It’s March 2018, and your Windows PC can be pwned by a web article (well, none of OURS)

Patch Tuesday Microsoft delivered another hefty bundle of patches with its scheduled monthly update.

Redmond bulks up for Vancouver

The March edition of Patch Tuesday lands just hours before researchers are expected to flaunt their latest and greatest exploits at the CanSecWest Pwn2Own hacking competition in Vancouver.

Hopefully nobody was planning to use any of the 75 CVE-listed vulnerabilities Microsoft addressed today, including several for the Edge and Internet Explorer browsers that would allow remote code execution.

The fixed bugs include nine remote code execution (RCE) flaws in the Chakra scripting engine in Edge. Microsoft says the scripting bugs (such as CVE-2018-0874) would allow an infected webpage to run code with the logged-in user’s clearance level.

The Edge scripting engine was also the subject of four memory corruption RCE flaws, as well as an information disclosure bug, CVE-2018-0839, that allows an attack page to view objects in memory.

Just two of the 75 Microsoft bugs squashed this month have been publicly disclosed. They include an elevation of privilege bug in Exchange (CVE-2018-0940) exploited via email. Dustin Childs of the Zero Day Initiative said that the bug is perfectly set up to facilitate a spear phishing attack.

“An attacker could use this vulnerability to replace a legitimate Outlook Web Access interface with a fake login page,” Childs explained.

“Once at the page, the user would be enticed to enter their real credentials.”

Also publically disclosed was a denial of service bug in ASP.NET (CVE-2018-0808) that would allow an attacker to take down a vulnerable web application remotely without authentication.

Childs said another interesting bug in this month’s bundle is CVE-2018-0868, an elevation of privilege bug in Windows Installer that allows an app to install unchecked libraries.

“At first glance, this doesn’t seem very crucial since an attacker would need the ability to run programs on a target system to exploit this vulnerability,” Childs said.

“However, this type of bug is often used by malware authors to “piggyback” their malicious code on top of innocuous code. It’s always easier to convince someone to install ‘GreatNewGame.exe’ instead of ‘EvilMalware.exe.’”

Elsewhere, Windows Kernel was found to contain 13 different CVE-listed flaws (such as CVE-2018-0811) that allow applications to view objects in memory, while 13 other entries were devoted to elevation of privilege bugs in SharePoint (like CVE-2018-0947) that are caused by SharePoint Server failing to properly verify tenant permissions.

Office was the subject of three CVE entries; a security feature bypass in Excel (CVE-2018-0907), an information disclosure bug from documents viewing out of bounds memory (CVE-2018-0919), and a remote code execution flaw (CVE-2018-0922) via a memory corruption error.

Quiet month for Adobe

By comparison, it was a slow month for Flash exploits. Adobe says the March fix for Flash Player only addresses two remote code execution flaws (CVE-2018-4919, CVE-2018-4920).

Adobe has also posted a fix for a pair of cross-site scripting bugs in Connect (CVE-2018-4921, CVE-2018-4923) exploited via SWF files, and a remote code execution flaw in Dreamweaver (CVE-2018-4924) for Windows exploited via command injection. ®

Sponsored:
Minds Mastering Machines – Call for papers now open

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2018/03/13/patch_tuesday_march_2018/

OK, deep breath, relax… Let’s have a sober look at these ‘ere annoying AMD chip security flaws

Analysis CTS-Labs, a security startup founded last year in Israel, sent everyone scrambling and headlines flying today – by claiming it has identified “multiple critical security vulnerabilities and manufacturer backdoors in AMD’s latest Epyc, Ryzen, Ryzen Pro, and Ryzen Mobile processors.”

Tuesday’s glitzy advisory disclosed no technical details – but described 13 “critical” security vulnerabilities that span four bug classes in AMD chips. The biz apparently gave AMD only one day of advance notice it was going public, an amount of time that precludes addressing the flaws prior to publication and deviates from security industry norms of responsible disclosure. Typically, organizations are given up to 30 to 90 days to fix their products.

The report describes the four classes of vulnerability, each of which has several variations. They all require local administrator access – or in one case, physical access – to exploit, which limits them as vulnerabilities useful for miscreants.

Essentially, the security holes can be exploited by malware already present in a computer to bury deep into its machinations to ensure it can’t be easily detected and removed – not even by wiping hard drives and reinstalling everything from scratch. The malware can inject itself into motherboard firmware to stay out of sight, all while meddling with or siphoning off files and other personal information, and interfering with system hardware.

But it’s important to note that a software nasty has to have superuser powers to abuse the programming cockups found by CTS-Labs. At which point, the malware already can spy on its victim, steal their data, hold their files to ransom, and so on.

The flaws do not open AMD-powered PCs and servers to remote hijacking over the internet, nor allow malicious apps to commandeer systems. Instead, they can be leveraged to ensure that once malware is present, it’s more difficult to find and remove.

Also, no code exploiting the security shortcomings has been made public, nor is any circulating right now in malware. The holes are also not necessarily unfixable.

What are the bug classes?

RYZENFALL allows malicious code to take over the AMD Secure Processor in Ryzen, Ryzen Pro, and Ryzen Mobile chips. Exploitation requires being able to run a program locally with administrator privileges. CTS-Labs claims there’s no mitigation, despite AMD’s recent released BIOS update that is supposed to disable the Secure Processor, thus killing off the whole thing.

The Secure Processor – aka the Platform Security Processor or PSP – is a coprocessor that ships with modern AMD chips that ensures a valid, untampered operating system is booted, among other tasks.

The RYZENFALL vulnerability may be related to a security issue in AMD’s Secure Processor reported by Google security researcher Cfir Cohen in January. RYZENFALL requires root-level access to attack. It can be used to commandeer the Secure Processor, boot backdoored operating systems, and extract, say, protected Bitlocker crypto-keys from the firmware to decrypt drives in seized Windows 10 machines.

FALLOUT, a flaw in the boot loader component of Epyc’s Secure Processor, allows attackers to read and write sensitive and protected memory areas, such as SMRAM and Windows Credential Guard isolated memory (VTL-1). As with RYZENFALL, local administrative access is necessary to exploit the issue.

CHIMERA is described as a pair of manufacturer backdoors, one in firmware and one in hardware (specifically in an ASIC), that allow code to be injected into AMD Ryzen chipsets. Again, you need root privileges to do this. This means the underlying motherboard firmware can be programmed to become a keylogger, send keypresses for passwords over the network, and so on.

The advisory claims the backdoors were introduced, accidentally or otherwise, by Taiwanese chip manufacturer ASMedia, owned by ASUSTeK, which used its own insecure integrated circuits in AMD’s Promontory chip, found in AMD’s Ryzen and Ryzen Pro lines.

MASTERKEY, allows the installation of persistent malware inside the Secure Processor, running in kernel-mode with administrative permissions. It requires the ability re-flash the motherboard BIOS with a malicious software update. This typically requires admin-level or physical access to a box, but CTS-Labs contends this could be done remotely through a command-line utility, again with the appropriate permissions.

The key thing with, er, MASTERKEY is that the system accepts modified BIOS images – when really, it ought to reject them, regardless of who is flashing them.

Eypc server chipsets are, we’re told, affected by FALLOUT and MASTERKEY. Ryzen workstation has CHIMERA, MASTERKEY and RYZENFALL. Ryzen Pro has CHIMERA and RYZENFALL. Ryzen mobile has RYZENFALL.

Questions of motivation

Some members of the online security community are characterizing the research as a hit piece designed to manipulate AMD’s stock price, presumably to benefit those intending to short company stock.

Dan Guido, CEO of security firm Trail of Bits, meanwhile contends the findings are valid. He said he was contacted by CTS-Labs ahead of today’s disclosures to check over the vulnerability discoveries to evaluate their impact, and said the blunders can be exploited. He was shown full technical details that have yet to be made public.

“Regardless of the hype around the release, the bugs are real, accurately described in their technical report (which is not public AFAIK), and their exploit code works,” he said via Twitter.

In a video published in conjunction with the research, Ido Li On, CEO of CTS-Labs, claimed many of Taiwanese chipmaker ASMedia’s products contain backdoors that could be used by hackers to inject malicious code. Fined by the FTC in 2016 for ignoring security flaws, ASMedia has helped build some AMD chipsets.

“When we looked at Ryzen computers, we saw that the very same backdoors that have existed on ASMedia chips for over six years are now on every Ryzen PC in the market,” Li On said. “This was deeply concerning to use and it got us to look at AMD security as a whole.”

Response

AMD in a statement issued a few hours ago said it was looking into the claims:

We have just received a report from a company called CTS-Labs claiming there are potential security vulnerabilities related to certain of our processors. We are actively investigating and analyzing its findings. This company was previously unknown to AMD and we find it unusual for a security firm to publish its research to the press without providing a reasonable amount of time for the company to investigate and address its findings.

In keeping with the practice cemented by the Spectre and Meltdown vulnerabilities in January, CTS-Labs is promoting the disclosure on a dedicated website, amdflaws.com – complete with logos, codenames, claims of public safety risks, and media briefings to create a big splash. No CVE ID numbers, though.

The website, and the white paper that accompanies it, includes a lengthy disclaimer advising not to use the research as investment advice. “The report and all statements contained herein are opinions of CTS and are not statements of fact,” the dot-com declared. “Organizations named in this website have not confirmed the accuracy or determined the adequacy of its contents.”

It also, curiously, acknowledges the possibility that those involved may have a financial interest in AMD stock:

Although we have a good faith belief in our analysis and believe it to be objective and unbiased, you are advised that we may have, either directly or indirectly, an economic interest in the performance of the securities of the companies whose products are the subject of our reports.

A separate website published under the name Viceroy Research meanwhile has cited CTS-Labs‘ work to claim, rather sensationally, “We believe AMD is worth $0.00 and will have no choice but to file for Chapter 11 (Bankruptcy) in order to effectively deal with the repercussions of recent discoveries.” Viceroy’s blog post and CTS’ findings went live today within a couple of hours of each other.

Reached by phone, John Fraser Perring, founder of Viceroy Research, which describes itself as “a group of individuals that see the world differently,” confirmed to The Register that his firm has a short position in AMD stock and that he intends to increase that position in light of support for CTS-Labs’ findings.

He said that technical experts he corresponded with who have verified the findings, specifically Dan Guido, have left him convinced that these flaws pose a serious risk to AMD customers.

Perring said he received a copy of report from an anonymous source and found the findings credible after consultation with internal and external technical experts.

Not everyone believes the flaws are quite so dire – certainly not enough to warrant a media blitz with claims of doom and death.

Sponsored:
Minds Mastering Machines – Call for papers now open

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2018/03/13/amd_flaws_analysis/

Russian anti-antivirus security tester pleads guilty to certifying attack code

A Russian coder who ran and franchised a dark web service that optimized malware and checked it against antivirus engines has pled guilty to one charge of conspiracy and one charge of aiding and abetting computer intrusion.

Jurijs Martisevs was arrested while on a trip to Latvia and extradited to the US after the authorities accused him and associate Ruslans Bondars of running the anti-antivirus system. Martisevs has now admitted to this, while Bondars is still awaiting trial.

According to court documents [PDF] Martisevs set up the service in 2009 and it operated until May 2017. Malware developers could submit their sample to the pair’s service and it would check the code against the virus signatures that are used by the world’s leading security software suites.

If the malware sample showed red and was likely to be identified in the wild, the code could then be tweaked to evade detection. One sample was submitted several times to the service before being unleashed on a major US retailer – thought to be Target.

Another malware writer with the initials ZS used the service to check the efficiency of a keylogger that had been developed. The malware was then sold to over 3,000 buyers and was thought to be used to infect over 16,000 computers.

The pair also offered their malware checking engine as an API so that it could be incorporated into off-the-shelf virus builder toolkits. Martisevs admitted that the code he helped develop was used by the Citadel malware that was used to extract $500m (£383m) from bank accounts around the world.

The pair even franchised out the service so other people could pitch it to hackers. They provided technical support via ICQ, Skype, Jabber, or email.

Martisevs faces a possible five years in prison on the conspiracy charge, along with a fine of $250,000 and three years’ supervised release. The aiding and abetting charge is more serious, with a possible ten years inside, as well as the fines and supervised release.

Under the terms of the plea deal [PDF] Martisevs has agreed to hand over more than $125,000 in profits that he earned over the eight-year period and to forfeit the computer hardware taken when he was arrested. In return he’ll be hoping for a shorter stay in the Big House. ®

Sponsored:
Minds Mastering Machines – Call for papers now open

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2018/03/14/russian_antiantivirus_security_tester_pleads_guilty_to_certifying_attack_code/

Let’s Encrypt updates certificate automation, adds splats

Let’s Encrypt has updated its certificate automation support and added Wildcard Certificates to its system.

Certificate automation replaces what are otherwise manual and ad hoc mechanisms to apply for an X.509 certificate, and for the applicant’s admins to prove they manage the domain in the certificate.

ACME is the automation standard Let’s Encrypt first wrote. It’s described here (the proposed version is in its tenth edit).

Written with input from Let’s Encrypt, Cisco, the EFF and the University of Michigan, the ACME v2 document says the manual certificate application process looks like this:

  • Create the certificate signing request (CSR) and paste it into a certificate authority’s (CA’s) Web page;
  • Prove domain ownership by answering a challenge from the CA (either on its Web page, in a DNS record, or via e-mail to an admin at the CA); and
  • Download and install the certificate.

ACME is designed to get rid of the “out-of-band” human interaction in the process, so that getting a CA-provided certificate is “nearly as easy to deploy … as with a self-signed certificate”, the standard says.

It uses JSON messages over HTTPS to carry the certificate action requests. Once a user has registered an ACME account, there are four steps to get a certificate: submit the order, prove you control the domain (the standard supports a number of challenge-response formats for this), submit a CSR, and download the issued certificate.

To use ACME for certificate automation, you need a compatible client. As well as Let’s Encrypt’s recommended Certbot, there’s a list of another 70-plus clients plus libraries for nine languages here.

The automated process is rate-limited under existing Let’s Encrypt rules, with an additional constraint. Applicants using the organisation’s ACME v2 endpoint are throttled to 300 new orders per three hours.

Josh Aas of the Internet Security Research Group announced the feature here, and noted that ACME support is needed for the second Let’s Encrypt feature announcement, Wildcard Certificates, which were expected in January.

For non-CA experts: Wildcard Certificates apply one certificate to multiple subdomains under a master domain. That way, if you needed to secure blogs.foo.com, images.foo.com, news.foo.com and www.foo.com with HTTPS, you can use a single certificate for all of them.

The DNS-01 challenge format secures wildcard applications, meaning admins will have to edit a DNS record to prove they have the right to request the certificate.

As this post explained, the ACME v2 RFC is still undergoing edits: “We intend to make our v2 endpoint implement the final ACME RFC, so there may be some further small changes, which we will pre-announce in the same API Announcements category as this post. We aim to keep these changes to a minimum”. ®

Sponsored:
Minds Mastering Machines – Call for papers now open

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2018/03/14/lets_encrypt_updates_certificate_automation_adds_splats/

SecurEnvoy SecurMail, you say? Only after this patch is applied, though

Recently resolved vulnerabilities in SecurEnvoy’s encrypted email transfer SecurMail created a way for encrypted emails in users’ inboxes to be read, overwritten and deleted by others.

The flaws – uncovered by Austrian security firm SEC Consult during a crash test – included cross-site scripting, cross-site request forgery, and missing authentication flaws. In order to send encrypted emails, a client did not need to authenticate on the SecurEnvoy server, according to SEC Consult. This opened the door for hackers to either extract all emails stored on the server or to modify messages.

Separate insecure direct object reference and path traversal vulnerabilities both created means for a “legitimate recipient to read mails sent to other users in plain text”.

“As we have identified several critical vulnerabilities within a very short time frame we expect numerous other vulnerabilities to be present,” SEC Consult’s Johannes Greil told The Register. “As other SecurEnvoy products (besides the analysed SecurMail) appear to be highly integrated (all products are installed with a single setup file) we suspect other components to also suffer from severe security deficits.”

In response to queries from El Reg, SecurEnvoy confirmed that it had patched SecurMail, adding that “this issue does not affect any other SecurEnvoy products”.

SEC Consult first notified SecurEnvoy about problems in SecurMail version 9.1.501 in late November. SecurEnvoy released a patch at the start of the month, clearing the way for SEC Consult to go public with an advisory.

SecurMail users are urged to upgrade as soon as possible by either applying the security patch 1_012018 or updating to version 9.2.501 of the software. ®

Sponsored:
Minds Mastering Machines – Call for papers now open

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2018/03/13/securenvoy_securmail_flaws/

It’s March 2018, and your PC can be pwned by reading an online article (well, none of OURS)

Patch Tuesday Microsoft delivered another hefty bundle of patches with its scheduled monthly update.

Redmond bulks up for Vancouver

The March edition of Patch Tuesday lands just hours before researchers are expected to flaunt their latest and greatest exploits at the CanSecWest Pwn2Own hacking competition in Vancouver.

Hopefully nobody was planning to use any of the 75 CVE-listed vulnerabilities Microsoft addressed today, including several for the Edge and Internet Explorer browsers that would allow remote code execution.

The fixed bugs include nine remote code execution (RCE) flaws in the Chakra scripting engine in Edge. Microsoft says the scripting bugs (such as CVE-2018-0874) would allow an infected webpage to run code with the logged-in user’s clearance level.

The Edge scripting engine was also the subject of four memory corruption RCE flaws, as well as an information disclosure bug, CVE-2018-0839, that allows an attack page to view objects in memory.

Just two of the 75 Microsoft bugs squashed this month have been publicly disclosed. They include an elevation of privilege bug in Exchange (CVE-2018-0940) exploited via email. Dustin Childs of the Zero Day Initiative said that the bug is perfectly set up to facilitate a spear phishing attack.

” An attacker could use this vulnerability to replace a legitimate Outlook Web Access interface with a fake login page,” Childs explained.

“Once at the page, the user would be enticed to enter their real credentials.”

Also publically disclosed was a denial of service bug in ASP.NET (CVE-2018-0808) that would allow an attacker to take down a vulnerable web application remotely without authentication.

Childs said another interested bug in this month’s bundle is CVE-2018-0868, an elevation of privilege bug in Windows Installer that allows an app to install unchecked libraries.

“At first glance, this doesn’t seem very crucial since an attacker would need the ability to run programs on a target system to exploit this vulnerability,” Childs said.

“However, this type of bug is often used by malware authors to “piggyback” their malicious code on top of innocuous code. It’s always easier to convince someone to install ‘GreatNewGame.exe’ instead of ‘EvilMalware.exe.’”

Elsewhere, Windows Kernel was found to contain 13 different CVE-listed flaws (such as CVE-2018-0811) that allow applications to view objects in memory, while 13 other entries were devoted to elevation of privilege bugs in SharePoint (like CVE-2018-0947) that are caused by SharePoint Server failing to properly verify tenant permissions.

Office was the subject of three CVE entries; a security feature bypass in Excel (CVE-2018-0907), an information disclosure bug from documents viewing out of bounds memory (CVE-2018-0919), and a remote code execution flaw (CVE-2018-0922) via a memory corruption error.

Quiet month for Adobe

By comparison, it was a slow month for Flash exploits. Adobe says the March fix for Flash Player only addresses two remote code execution flaws (CVE-2018-4919, CVE-2018-4920).

Adobe has also posted a fix for a pair of cross-site scripting bugs in Connect (CVE-2018-4921, CVE-2018-4923) exploited via SWF files, and a remote code execution flaw in Dreamweaver (CVE-2018-4924) for Windows exploited via command injection. ®

Sponsored:
Minds Mastering Machines – Call for papers now open

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2018/03/13/patch_tuesday_march_2018/