php-laminas-diactoros2-2.12.0-1.fc36

Read Time:2 Minute, 31 Second

FEDORA-2022-42c54e9e5f

Packages in this update:

php-laminas-diactoros2-2.12.0-1.fc36

Update description:

Version 2.12.0

Bug

99: Merge release 2.11.3 into 2.12.x thanks to @github-actions[bot]
92: Fix typo in property name in UploadedFileTest::setUp() thanks to @TimWolla

Enhancement

97: Ignore obviously malformed host headers when constructing a ServerRequest thanks to @TimWolla
91: Fix typo thanks to @PhantomWatson

Version 2.11.3

Bug, Enhancement

98: Fixed UploadedFile::moveTo() so it actually removes the original file when used in CLI context, and doesn’t leave orphaned files thanks to @k2rn

Version 2.11.2

Bug

95: Resolve Host header and X-Forwarded-Proto regressions thanks to @weierophinney

Release Notes for 2.11.1

This is a SECURITY release. All users are encouraged to upgrade immediately.

Added

This release adds features to allow filtering a ServerRequest as generated by LaminasDiactorosServerRequestFactory::fromGlobals() for the purposes of initialization. Examples include:

Adding a request identifier.
Using X-Forwarded-* headers to modify the URL to represent the original client request.

The features are based on a new interface, LaminasDiactororsServerRequestFilterFilterServerRequestInterface, which defines a single method:

public function __invoke(
PsrHttpMessageServerRequestInterface $request
): PsrHttpMessageServerRequestInterface

We provide two implementations, as follows:

LaminasDiactorosServerRequestFilterDoNotFilter will return the provided request verbatim.
LaminasDiactorosServerRequestFilterFilterUsingXForwardedHeaders has named constructors that allow you to define how and when X-Forwarded- headers are used to modify the URI instance associated with the request. These methods are:
* trustAny(): this method generates a filter instance that will trust all X-Forwarded-
headers from any source.
* trustReservedSubnets(array $trustedHeaders = ?): this method generates a filter instance that only modifies the URL if the IP address of the requesting server is from a reserved, private subnet (localhost; classes A, B, and C subnets; and IPv6 private and local-link subnets). By default, it will trust all X-Forwarded- headers from these sources, but you may specify a list to allow via the $trustedHeaders argument.
* trustProxies(array $proxyCIDRList, array $trustedHeaders = ?): this method will generate a filter instance that only modifies the URL if the requesting server matches an entry in the $proxyCIDRList. These entries may be IP addresses, or any IPv4 or IPv6 CIDR subnets. By default, it will trust all X-Forwarded-
headers from these sources, but you may specify a list to allow via the $trustedHeaders argument.

ServerRequestFactory::fromGlobals() now accepts a FilterServerRequestInterface instance as the optional argument $requestFilter. If none is provided, it uses one as produced by FilterUsingXForwardedHeaders::trustReservedSubnets().

Deprecated

The function LaminasDiactorosmarshalUriFromSapi() is deprecated, and no longer used internally.

Changed

LaminasDiactorosServerRequestFactory::fromGlobals() no longer consumes marshalUriFromSapi(), and instead inlines an alternate implementation. The new implementation does not consider X-Forwarded- headers by default when generating the associated URI instance. Internally, if no FilterServerRequestInterface implementation is provided, it defaults to using an instance returned by FilterUsingXForwardeHeaders::trustReservedSubnets(). If you previously relied on X-Forwarded- headers, you MAY need to update your code to use either the FilterUsingXForwardedHeaders::trustAny() or FilterUsingXForwardedHeaders::trustProxies() methods to generate a filter to use with ServerRequestFactory::fromGlobals().

Fixed

Fixes CVE-2022-31109

Read More

Comprehensive risk-based API protection with AppTrana

Read Time:19 Second

Graham Cluley Security News is sponsored this week by the folks at Indusface. Thanks to the great team there for their support! It is hard to imagine an application without APIs (Application Programming Interface). For the past few years, APIs have become core foundational for the success of businesses. Hence, there is no surprise that … Continue reading “Comprehensive risk-based API protection with AppTrana”

Read More

CVE-2021-45721

Read Time:19 Second

JFrog Artifactory prior to version 7.29.8 and 6.23.38 is vulnerable to Reflected Cross-Site Scripting (XSS) through one of the XHR parameters in Users REST API endpoint. This issue affects: JFrog JFrog Artifactory JFrog Artifactory versions before 7.36.1 versions prior to 7.29.8; JFrog Artifactory versions before 6.23.41 versions prior to 6.23.38.

Read More

CVE-2021-23163

Read Time:16 Second

JFrog Artifactory prior to version 7.33.6 and 6.23.38, is vulnerable to CSRF ( Cross-Site Request Forgery) for specific endpoints. This issue affects: JFrog JFrog Artifactory JFrog Artifactory versions before 7.33.6 versions prior to 7.x; JFrog Artifactory versions before 6.23.38 versions prior to 6.x.

Read More

AT&T Cybersecurity Insights Report: A Focus on SLED

Read Time:5 Minute, 28 Second

The public servants and educators that keep state and local governments and higher education institutions running stand at the nexus of change. They’re tasked with providing citizens with new services that account for rapid changes in the tech landscape and societal processes, while maintaining the same rock-solid dependability, security, and safety that people have expected of governing bodies for generations. 

In the latest industry breakout of the AT&T Cybersecurity Insights Report, we examine how state and local government and higher education (SLED) organizations have stood up to these trending challenges. Released today, AT&T Cybersecurity Insights Report: Securing the Edge-A Focus on SLED shows that this sector is a leader, of those surveyed, in innovating at the edge and is investing significantly in cybersecurity as it does so. With the stakes high for citizens, students, and the public at large, SLED is moving rapidly to the edge to satisfy new use cases and to optimize its security strategy to realistically balance risk reduction against budgetary realities. The following is a synopsis of our analysis in this new report focused on SLED.

Filling the needs of citizen users

The push for digital transformation across the private sector is similarly influencing public sector entities in the SLED vertical. Technology leaders at these organizations are being pushed to serve citizens as they would consumers, with user experience top-of-mind.

Whether it is in supporting city infrastructure with smart electric capabilities, enabling virtual classes and government services, improving digital services at remote government offices, or building out secure, cutting-edge connectivity on campus, SLED is being asked to move the bar quickly on digital transformation. The pressure to do so has been particularly amplified in the last year as societal changes caused by the COVID-19 pandemic has driven many of these organizations to completely rethink processes and citizen touch points to provide better options for remote, virtual, and contactless interactions.

Edge computing is playing a pivotal role in SLED’s movement toward digital-first operating models.

SLED is a leading sector of edge innovation

A new compute paradigm underpinned by 5G technology, edge computing drives distributed architectures that put applications, workloads, and hosting closer to users and assets that generate or consume data. Analysis for the broader 2022 AT&T Cybersecurity Insight Report looked at edge compute adoption phases across the six markets surveyed, breaking the state of edge use cases into early stage (ideation and researching), mid-stage (planning and proof of concept), and mature stage (partial and full implementation).

In this research, our analysis found that compared to other sectors such as energy, finance healthcare, and retail, SLED was ahead of many of them in edge deployment. The report’s analysis showed that SLED:

ranked first in mature stage adoption of edge use cases
ranked third in mid-stage adoption of edge use cases

Sorting through the specific use cases in these categories, the most prevalent edge use case that SLED was farthest along in within that mature stage was to support public safety and enforcement, namely in deploying technology for gunshot detection and surveillance. Some organizations are seeking to further bolster that technology with future pairing of these notifications for first-responders with real-time traffic analysis and control to further speed up their time of response to life-saving situations. Meantime, the most prevalent use case in the mid-stage was the automation of public services, including support for smart meters for utilities such as water, gas, or electricity.

The rollout of these digital services is clearly for the betterment of communities. But adding digital layers to critical infrastructure and processes also adds risk. Which means that appropriate cybersecurity controls to protect SLED’s growing edge compute deployments for everything from mass transit optimization to electronic voting requires careful cybersecurity planning and execution.

SLED operates with slim margin for mistakes

The true value of edge innovation in SLED institutions is only gained when these organizations can ensure the trust of citizens that their use of cutting-edge devices is safe, secure, and financially responsible. The good news is that this sector leads in number of use cases, and the rate at which it is investing in securing them:

67% or more SLED survey respondents report they are investing greater than 11% of their overall edge project budget for security
76% of state and  local governments indicate investments of 11% or more directly tallied to cybersecurity

That’s in contrast to finance, for which just 59% of respondents said they’ve allocated similar percentages of their budgets to security.

Many of the public sector organizations in the SLED contingent struggle with getting the most out of these security investments and the underlying edge project budget. The report showed that survey respondents in this vertical reported the lowest perceived effectiveness for their spend. Often the state and local governments in this group are called to pay closer attention to spending and efficiency. They’re closer to their local constituents than, say, their counterparts at the federal level and have less margin for error—both in fulfilling their security and fiduciary responsibilities. Local elections come quickly and constituents offer vocal scrutiny when government services are disrupted due misspending, bungled deployments, or security breaches.

Many in the SLED sector are answering these questions by combining cybersecurity and network functions in the cloud with technology such as SASE to future-proof their edge security. Approximately 52.4% of SLED respondents said they would move toward this route, compared to 45.7% that would combine them on-premises. This preference for cloud likely has to do with the need that many of these organizations have to be budget conscious, paying attention to their internal ability to affordably manage security as deployments grow more complex. Unsurprisingly, SLED respondents judged the security effectiveness and efficiency highest for those technologies related to this architectural philosophy. For example, Zero Trust network access control was ranked the number one most efficient security control at their disposal.

As SLED organizations grapple with the trends outlined here, we recommend that they talk with service providers and network operators prior to making decisions about edge networking and security. A trusted advisor can help architects discuss the pros and cons of public and private 5G cellular, legacy cellular, remote office/branch office, IaaS/PaaS/SaaS cloud environment, industrial IoT/OT, or consumer IoT environments. Together these organizations can work with a provider to develop realistic scenarios for incremental transitions to 5G and edge computing that maximizes benefits and minimizes risk.

Read More

How to keep attackers from using PowerShell against you

Read Time:42 Second

Living off the land is not the title of a gardening book. It’s the goal of attackers going after your network. Rather than installing malicious software on your network that antivirus software might flag, attackers use the code already there to launch attacks. The tools that you use to monitor, maintain and access your network are often the same code that attackers use to attack your network. PowerShell is a prime example.

The U.S. National Security Agency (NSA), U.S. Cybersecurity and Infrastructure Security Agency (CISA), New Zealand’s NCSC, and the UK NCSC recently released a document called Keeping PowerShell: Security Measures to Use and Embrace. This guidance recommends keeping PowerShell in your network rather than blocking but offers the following advice to keep it secure.

To read this article in full, please click here

Read More

What is decentralized identity?

Read Time:32 Second

Decentralized identity (DID) challenges some core assumptions about how online authentication works.  In particular, the idea that a third-party authority is required to manage the sensitive data that comprises identity.  DID holds out the promise of reducing reliance on such authority and returning some degree of control of the data to the data’s owner, with possible privacy and accessibility boons.

Traditionally, digital identity is maintained by organizations trusted to secure that information in their datastores.  This model has, over time, revealed itself to be subject to several shortcomings.  These shortcomings can be overviewed as follows:

To read this article in full, please click here

Read More

NIST names new post-quantum cryptography standards

Read Time:45 Second

The path to a secure future in a world with quantum computers just became a bit clearer. This week, the U.S. National Institute of Standards and Technology (NIST) announced the algorithms that were chosen in the third round of its competition to create a new post-quantum cryptography (PQC) standard built upon encryption algorithms that can resist the powers of quantum processors.

NIST made an announcement with several layers. At the core were the choices for the main algorithms: CRYSTALS-Kyber for establishing a key and CRYSTALS-Dilithium for digital signatures. Both share the same theoretical approach which could make it simpler to implement both concurrently. NIST also announced that the digital signatures algorithms Falcon and SPHINCS+ would be standardized. It will also continue to study several other algorithms and perhaps standardize them during the fourth round of the competition.

To read this article in full, please click here

Read More