Connect with us

Technology

AWS fixes file vuln on internal credential access for RDS • The Register

Voice Of EU

Published

on

A local file read vulnerability in Amazon’s Relational Database Service (RDS) could be exploited to allow an attacker to gain access to internal AWS credentials, the cloud behemoth has confirmed.

Cloud security company Lightspin’s research team discovered the flaw and reported it to AWS, which applied an initial patch and worked with customers to mitigate the vulnerability.

While no in-the-wild attacks exploited the bug, AWS confirmed it gave researchers access “to internal credentials that were specific to their Aurora cluster.”

“No cross-customer or cross-cluster access was possible; however, highly privileged local database users who could exercise this issue could potentially have gained additional access to data hosted in their cluster or read files within the operating system of the underlying host running their database,” according to the AWS security bulletin.

After Lightspin alerted the cloud giant to the flaw, AWS “moved immediately” to fix the issue. This included updating Amazon Aurora PostgreSQL and Amazon RDS for PostgreSQL. It also deprecated some older versions of both products, which means customers can’t create new instances with these versions.

In a blog post, Lightspin Director of Security Research Gafnit Amiga detailed how she exploited the vulnerability on the RDS EC2 instance using the log_fdw extension.

The log_fdw extension lets users access the database engine log using a SQL interface and build foreign tables. Versions 9.6.2 and higher of Amazon RDS for PostgreSQL engines support this extension.

Amiga discovered that a user could bypass the the  log_fdw extension validation by dropping the validator function: ALTER FOREIGN DATA WRAPPER log_fdw NO VALIDATOR;

Extension validation happens in the validator function, the handler function, or both. But because the validator function is optional, it can be dropped without damaging the functionality. This allows the user to create a table without validation in the handler function.

From here, Amiga poked around in system files until she found one with the following temporary credentials: CSD_GROVER_API_CREDENTIALS. 

As she explained:

Amiga exported the access key, secret access key, and session token using the AWS Security Token Service’s (STS) GetCallerIdentity API. This gave her the user ID, account ID, and Amazon Resource Name (ARN) for identity and access management (IAM) credentialsand this provided access to an internal AWS service.  

“This is where my analysis and research ended,” Amiga wrote. “I did not attempt to enumerate any IAM permissions or move further laterally into AWS’ internal environment.”

Lightspin reported the vuln to AWS on December 9, and five days later the cloud provider deployed an initial patch while working on a full fix. 

By late March, AWS had reached out to all of its affected customers and fixed all supported versions of Amazon Aurora PostgreSQL and Amazon RDS for PostgreSQL.

“The AWS Cloud is a blessing for many developers, architects, and security professionals around the world due to its pay-as-you-go model and diversity of service offerings,” Amiga concluded. “However, like any service provider, wrapping third-party services such as PostgreSQL and trying to provide users with advanced features is sometimes a double-edged sword.” ®

Source link

Technology

US offers $10m reward for info on five Conti ransomware members

Voice Of EU

Published

on

Rewards for Justice shared a photo of someone it claims to be an associate of the ransomware gang and is offering a reward to identify him and four others.

The US Department of State is offering a $10m reward for any information on five malicious cyber actors who are believed to be high-ranking members of the Conti ransomware gang.

The US has been offering rewards for information on this ransomware gang since May, including a $5m reward for any intel that leads to the arrest of anyone conspiring or attempting to participate in a Conti attack.

Yesterday (11 August), the department’s Rewards for Justice programme shared an alleged photo of an associate of the ransomware gang. The department said on Twitter that it is “trying to put a name to the face” and believes the individual is the hacker known as “Target”.

Illustration showing an image of a man with four figures next to it. A reward offer for information on the Conti ransomware gang.

A request for information by the Rewards for Justice programme. Image: US Department of State/Rewards for Justice

Conti, also known as Wizard Spider, has been linked to a group believed to be based near St Petersburg, Russia. The US has labelled it a “Russian government-linked ransomware-as-a-service (RaaS) group”.

The group’s malware is believed to be responsible for more than 1,000 ransomware operations targeting critical infrastructure around the world, from law enforcement agencies to emergency medical services and dispatch centres.

In May 2021, the Conti group was behind the HSE ransomware incident that saw more than 80pc of the IT infrastructure of healthcare services across Ireland impacted. It was said to be the most serious cyberattack ever to hit the State’s critical infrastructure.

The US Department of State previously said the Conti ransomware variant is the “costliest strain of ransomware” ever documented. The FBI estimates that, as of January 2022, there had been more than 1,000 victims of attacks associated with Conti ransomware, with victim payouts exceeding $150m.

When Russia began its invasion of Ukraine earlier this year, the Conti group declared its allegiance to the Russian government. Shortly after, a Ukrainian researcher took the cybersecurity world by storm after publishing more than 60,000 internal messages of the ransomware gang.

Raj Samani, chief scientist at cybersecurity firm Rapid7, said the latest reward offer is just “the tip of the iceberg as enforcement agencies make “considerable strides” through public-private collaboration to hold cybercriminals to account.

“Announcing a reward and revealing the details of Conti members sends a message to would-be criminals that cybercrime is anything but risk-free,” said Samani.

10 things you need to know direct to your inbox every weekday. Sign up for the Daily Brief, Silicon Republic’s digest of essential sci-tech news.



Source link

Continue Reading

Technology

Meditation app Calm sacks one-fifth of staff | Meditation

Voice Of EU

Published

on

The US-based meditation app Calm has laid off 20% of its workforce, becoming the latest US tech startup to announce job cuts.

The firm’s boss, David Ko, said the company, which has now axed about 90 people from its 400-person staff, was “not immune” to the economic climate. “In building out our strategic and financial plan, we revisited the investment thesis behind every project and it became clear that we need to make changes,” he said in a memo to staff.

“I can assure you that this was not an easy decision, but it is especially difficult for a company like ours whose mission is focused on workplace mental health and wellness.”

The Calm app, founded in 2012, offers guided meditation and bedtime stories for people of all ages. It received a surge of downloads triggered by the 2020 Covid lockdowns. By the end of that year, the software company said the app had been downloaded more than 100 million times globally and had amassed over 4 million paying subscribers.

Investors valued the firm, which said it had been profitable since 2016, at $2bn.

In the memo, Ko went on: “We did not come to this decision lightly, but are confident that these changes will help us prioritize the future, focus on growth and become a more efficient organization.”

More than 500 startups have laid off staff this year, according to layoffs.fyi, a website that tracks such announcements.

Source link

Continue Reading

Technology

Let there be ambient light sensing, without data theft • The Register

Voice Of EU

Published

on

Six years after web security and privacy concerns surfaced about ambient light sensors in mobile phones and notebooks, browser boffins have finally implemented defenses.

The W3C, everyone’s favorite web standards body, began formulating an Ambient Light Events API specification back in 2012 to define how web browsers should handle data and events from ambient light sensors (ALS). Section 4 of the draft spec, “Security and privacy considerations,” was blank. It was a more carefree time.

Come 2015, the spec evolved to include acknowledgement of the possibility that ALS might allow data correlation and device fingerprinting, to the detriment of people’s privacy. And it suggested that browser makers might consider event rate limiting as a potential mitigation.

By 2016, it became clear that allowing web code to interact with device light sensors entailed privacy and security risks beyond fingerprinting. Dr Lukasz Olejnik, an independent privacy researcher and consultant, explored the possibilities in a 2016 blog post.

Olejnik cited a number of ways in which ambient light sensor readings might be abused, including data leakage, profiling, behavioral analysis, and various forms of cross-device communication.

He described a few proof-of-concept attacks, devised with the help of security researcher Artur Janc, in a 2017 post and delved into more detail in a 2020 paper [PDF].

“The attack we devised was a side-channel leak, conceptually very simple, taking advantage of the optical properties of human skin and its reflective properties,” Olejnik explained in his paper.

“Skin reflectance only accounts for the 4-7 percent emitted light but modern display screens emit light with significant luminance. We exploited these facts of nature to craft an attack that reasoned about the website content via information encoded in the light level and conveyed via the user skin, back to the browsing context tracking the light sensor readings.”

It was this technique that enabled the proof-of-concept attacks like stealing web history through inferences made from CSS changes and stealing cross origin resources, such as images or the contents of iframes.

Snail-like speed

Browser vendors responded in various ways. In May 2018, with the release of Firefox 60, Mozilla moved access to the W3C proximity and ambient light APIs behind flags, and applied further limitations in subsequent Firefox releases.

Apple simply declined to implement the API in WebKit, along with a number of other capabilities. Both Apple and Mozilla currently oppose a proposal for a generic sensor API.

Google took what Olejnik described his paper as a “more nuanced” approach, limiting the precision of sensor data.

But those working on the W3C specification and on the browsers implementing the spec recognized that such privacy protections should be formalized, to increase the likelihood the API will be widely adopted and used.

So they voted to make the imprecision of ALS data normative (standard for browsers) and to require the camera access permission as part of the ALS spec.

Those changes finally landed in the ALS spec this week. As a result, Google and perhaps other browser makers may choose to make the ALS API available by default rather than hiding it behind a flag or ignoring it entirely. ®



Source link

Continue Reading

Trending

Subscribe To Our Newsletter

Join our mailing list to receive the latest news and updates 
directly on your inbox.

You have Successfully Subscribed!