<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: johnettagaweraks</title>
    <description>The latest articles on DEV Community by johnettagaweraks (@johnettagaweraks).</description>
    <link>https://dev.to/johnettagaweraks</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4214752%2Fa63d1043-8027-441d-9139-c0c5351c2f12.png</url>
      <title>DEV Community: johnettagaweraks</title>
      <link>https://dev.to/johnettagaweraks</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/johnettagaweraks"/>
    <language>en</language>
    <item>
      <title>OpenAppSec's low fingerprint count hides a distributed management path</title>
      <dc:creator>johnettagaweraks</dc:creator>
      <pubDate>Wed, 18 Nov 2026 23:22:05 +0000</pubDate>
      <link>https://dev.to/johnettagaweraks/openappsecs-low-fingerprint-count-hides-a-distributed-management-path-358a</link>
      <guid>https://dev.to/johnettagaweraks/openappsecs-low-fingerprint-count-hides-a-distributed-management-path-358a</guid>
      <description>&lt;h1&gt;
  
  
  OpenAppSec's low fingerprint count hides a distributed management path
&lt;/h1&gt;

&lt;p&gt;OpenAppSec deploys agents near web applications and can manage policy through a central Web UI, a local policy file, or declarative configuration. The agent may not advertise the product name in an HTTP title. The management path can therefore matter more than a public search result, especially when one profile controls several agents and assets.&lt;/p&gt;

&lt;h2&gt;
  
  
  What ZoomEye returned
&lt;/h2&gt;

&lt;p&gt;The count-only probe ran on 2026-11-18 at 22:44 UTC with &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and pagesize 1. Results were:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;app="OpenAppSec"&lt;/code&gt;: 0 matches.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;title="OpenAppSec"&lt;/code&gt;: 1 match.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;http.body="OpenAppSec"&lt;/code&gt;: 18 matches.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The results are very small. They could be a login page, documentation, or unrelated text. They do not describe the installed agent population. The query should be repeated with the same scope if an analyst needs a trend, but the current set is best treated as a lead for manual ownership checks.&lt;/p&gt;

&lt;h2&gt;
  
  
  Agent, profile, and asset
&lt;/h2&gt;

&lt;p&gt;OpenAppSec documentation separates agents from the policies they receive. An agent registers with a management profile, receives a policy version, and may appear as disconnected when communication stops. The management UI tracks agents and profiles. A policy can be managed centrally or locally, and the choice changes which system is authoritative.&lt;/p&gt;

&lt;p&gt;Inventory every deployment token and profile. Confirm which assets or sites the profile covers and whether agents are allowed to receive policies for other assets. Review the communication channel between agent and management, the certificate or token used for registration, and the procedure for removing a disconnected agent. A stale agent with a copied token is a durable trust relationship even when it no longer appears in the UI.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review change authority
&lt;/h2&gt;

&lt;p&gt;In management mode, the Web UI, GraphQL API, and infrastructure-as-code path can all change effective policy. Check role separation for profile creation, publishing, and deletion. The documentation describes a publish step for making changes visible to other administrators and enforcing policy. Separate drafting from publication so a partial change does not silently become production state.&lt;/p&gt;

&lt;p&gt;In declarative mode, protect the mounted local policy and the automation that updates it. Restarting an agent after a policy change can create an availability event, while automatic reload can apply a bad rule without a restart review. Record the agent version, profile version, policy digest, and last contact time.&lt;/p&gt;

&lt;p&gt;The external count is a weak population signal. The stronger evidence is the relationship between an active agent, its profile, its assets, and the identity that can publish a new policy.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.zoomeye.ai/searchResult?q=aHR0cC5ib2R5PSJPcGVuQXBwU2VjIg%3D%3D" rel="noopener noreferrer"&gt;ZoomEye query: http.body="OpenAppSec"&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.openappsec.io/concepts/management-and-automation" rel="noopener noreferrer"&gt;OpenAppSec: Management and automation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.openappsec.io/management-web-ui/track-agent-status" rel="noopener noreferrer"&gt;OpenAppSec: Track agent status&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.openappsec.io/getting-started/using-the-web-ui-saas" rel="noopener noreferrer"&gt;OpenAppSec: Using the Web UI&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>zoomeye</category>
      <category>openappsec</category>
      <category>waf</category>
      <category>managementplane</category>
    </item>
    <item>
      <title>Tomcat Manager is application deployment authority behind a login page</title>
      <dc:creator>johnettagaweraks</dc:creator>
      <pubDate>Wed, 18 Nov 2026 20:01:20 +0000</pubDate>
      <link>https://dev.to/johnettagaweraks/tomcat-manager-is-application-deployment-authority-behind-a-login-page-1i61</link>
      <guid>https://dev.to/johnettagaweraks/tomcat-manager-is-application-deployment-authority-behind-a-login-page-1i61</guid>
      <description>&lt;h1&gt;
  
  
  Tomcat Manager is application deployment authority behind a login page
&lt;/h1&gt;

&lt;p&gt;Apache Tomcat includes a Manager web application for deploying and managing web applications. The Manager documentation describes operations for application status, deployment, undeployment, starting and stopping applications, session inspection, and diagnostics. A reachable Manager interface is therefore a deployment control plane. The login page is not the whole boundary. The role assigned after login decides whether the user can read status, deploy a WAR, or manage another application.&lt;/p&gt;

&lt;p&gt;The ZoomEye measurements show why a generic path can mislead. With &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and page size 1, &lt;code&gt;title="Tomcat Manager"&lt;/code&gt; returned 3, &lt;code&gt;app="Tomcat Manager"&lt;/code&gt; returned 0, and &lt;code&gt;http.body="/manager/html"&lt;/code&gt; returned 3,334,098. The body count is dominated by documentation, tutorials, logs, and pages that mention the standard path. It is not a count of exposed Manager applications. The title count is small, and the application field provides no useful fingerprint in this sample.&lt;/p&gt;

&lt;h2&gt;
  
  
  Roles matter more than the URL
&lt;/h2&gt;

&lt;p&gt;Tomcat Manager defines distinct roles for GUI, script, JMX proxy, and status access. A status role should not be able to deploy an application. A script role may be intended for automation but can still change the deployed surface. Review the &lt;code&gt;tomcat-users.xml&lt;/code&gt; or external realm configuration, the role mappings, and the accounts that can reach the Manager context.&lt;/p&gt;

&lt;p&gt;The Manager and Host Manager are separate applications. An inventory should record both paths and the roles behind them. A proxy that protects &lt;code&gt;/manager/html&lt;/code&gt; may not protect &lt;code&gt;/manager/text&lt;/code&gt;, &lt;code&gt;/host-manager/html&lt;/code&gt;, or a custom context path. Verification should test the exact route and method that the organization intends to allow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Treat deployment as code execution
&lt;/h2&gt;

&lt;p&gt;A user who can deploy a web application can usually cause server-side code to run under the Tomcat service identity. That is the intended function of the Manager. The security concern is not a hidden bug in the page title. It is whether the deployment authority is appropriately limited, authenticated, and monitored.&lt;/p&gt;

&lt;p&gt;If the Manager is needed for production operations, bind it to a management network and require strong authentication and TLS. Restrict deployment roles to a named automation account. Keep the Tomcat service account with the least privilege needed for its web applications and deployment directory. Do not run Tomcat as root to make file deployment easier.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build an ownership record
&lt;/h2&gt;

&lt;p&gt;For each Tomcat instance, record the host, Tomcat version, connector ports, Manager and Host Manager paths, authentication realm, allowed roles, and the applications that can be deployed. Compare the current deployed applications with the release inventory. A Manager status page can show session and application information that is useful during an incident, but it is also a map of the service.&lt;/p&gt;

&lt;p&gt;Monitor Manager logins, deployment attempts, application state changes, and failed role checks. Alert on access from outside the management network. A successful login by a service account is not enough evidence that the account is healthy. Confirm its role, recent change ticket, and source address.&lt;/p&gt;

&lt;p&gt;The body count of 3,334,098 should not be used as an exposure headline. It demonstrates that &lt;code&gt;/manager/html&lt;/code&gt; is a familiar string in indexed content. The useful work is to identify which of those references are actual Tomcat hosts, then determine whether their Manager context is reachable and which role protects it.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://tomcat.apache.org/tomcat-10.1-doc/manager-howto.html" rel="noopener noreferrer"&gt;Tomcat Manager App How-To&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.zoomeye.ai/" rel="noopener noreferrer"&gt;ZoomEye&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>zoomeye</category>
      <category>tomcat</category>
      <category>manager</category>
      <category>applicationdeployment</category>
    </item>
    <item>
      <title>Verifying Adobe Campaign Classic Remediation After the Patch</title>
      <dc:creator>johnettagaweraks</dc:creator>
      <pubDate>Wed, 18 Nov 2026 16:41:52 +0000</pubDate>
      <link>https://dev.to/johnettagaweraks/verifying-adobe-campaign-classic-remediation-after-the-patch-243b</link>
      <guid>https://dev.to/johnettagaweraks/verifying-adobe-campaign-classic-remediation-after-the-patch-243b</guid>
      <description>&lt;h1&gt;
  
  
  Verifying Adobe Campaign Classic Remediation After the Patch
&lt;/h1&gt;

&lt;p&gt;A security update can appear complete while an old Campaign Classic build remains in service. The Adobe fix for CVE-2026-104350 is 7.4.4 build 9403, and the same release addresses seven other critical CVEs in APSB26-162. Verification should prove the running build and the operating state, not just that a file was installed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Confirm the deployed build
&lt;/h2&gt;

&lt;p&gt;Read the version from the Campaign application after the update. Record the exact build string, timestamp, environment, host, and observer. Compare it with the vendor's corrected release and with the deployment record. A package repository that contains the installer is not evidence that production is running it.&lt;/p&gt;

&lt;p&gt;On a multi-server deployment, check every application server and the management components that participate in the affected service. If a load balancer can send traffic to a host that was missed, the security state is inconsistent. Take inventory of old nodes before they rejoin a pool.&lt;/p&gt;

&lt;p&gt;Build verification should include staging and disaster-recovery systems that can become production. A standby system left at build 9402 can expand the exposure during a failover. Document whether each standby is patched, isolated, or scheduled for a later window.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the application, not only the version
&lt;/h2&gt;

&lt;p&gt;After the restart, test authentication, application navigation, Campaign workflows, audience access, template rendering, and delivery connections. Use a non-sending mode where possible. Confirm that scheduled jobs and approved integrations are running with the permissions they need.&lt;/p&gt;

&lt;p&gt;Review the database connection and any release-specific changes in Adobe's instructions. A service can report the new build while a database or connector failure leaves critical functions unavailable. The verification should identify that state before users discover it during a campaign launch.&lt;/p&gt;

&lt;p&gt;Inspect application logs for errors that appeared after the update. Compare the error rate with the pre-change baseline. A small number of expected startup warnings is different from repeated workflow or authentication failures.&lt;/p&gt;

&lt;h2&gt;
  
  
  Validate that the other CVEs are covered
&lt;/h2&gt;

&lt;p&gt;The same update includes command injection, OS command injection, incorrect authorization, and SQL injection issues. The vendor groups these fixes under build 9403. A team that has verified the build has evidence that the supported update was installed, but it still needs to review the application behavior relevant to its integrations.&lt;/p&gt;

&lt;p&gt;Do not invent a test suite from the advisory. Adobe has not published the affected parameter for CVE-2026-104350, and the bulletin does not provide a public exploit for every CVE. A responsible verification can include vendor-supported health checks, configuration review, and monitoring rather than trying to weaponize unverified paths in production.&lt;/p&gt;

&lt;h2&gt;
  
  
  Reconcile inventory and ownership
&lt;/h2&gt;

&lt;p&gt;A ZoomEye query for &lt;code&gt;title="Adobe Campaign"&lt;/code&gt; returned 149 page-title matches during this review. These are product-related pages, not proof that any host is vulnerable. Use the result to locate public Campaign interfaces, then reconcile them with application owners and build records.&lt;/p&gt;

&lt;p&gt;The exact CVE filter returned zero. That does not prove there are no affected Campaign systems. It confirms that the selected public query did not identify assets by CVE. Internal inventory and authenticated build checks remain necessary.&lt;/p&gt;

&lt;p&gt;For every system, record one of these outcomes: build 9403 or later, affected build, unknown build, or unable to locate the owner. Unknown is not complete. Give each unknown item a path to verification and a responsible team.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review access after the change
&lt;/h2&gt;

&lt;p&gt;A patched application is still an exposed application. Review which networks can reach Campaign, who has administrative roles, and whether old service accounts or vendor paths remain active. Remove temporary test accounts and stale firewall exceptions created during the maintenance window.&lt;/p&gt;

&lt;p&gt;Recheck content security headers, reverse-proxy policy, TLS configuration, and authentication settings where the deployment uses them. These controls may have been disabled for troubleshooting and must be restored before closure. A control that is not tested after the patch may exist only in the change description.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep monitoring for post-patch evidence
&lt;/h2&gt;

&lt;p&gt;Retain logs and detections after the build change. Look for unexpected script content in Campaign requests, repeated authorization failures, unusual exports, changes to user roles, and modifications to campaigns or delivery settings. Correlate suspicious activity with the patch timeline.&lt;/p&gt;

&lt;p&gt;Adobe was not aware of in-the-wild exploitation for APSB26-162 when the bulletin was published. That statement supports context but does not replace local detection. If earlier activity is found, determine whether it preceded the update and whether any session or account action followed it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Close related products explicitly
&lt;/h2&gt;

&lt;p&gt;APSB26-182 is a separate Adobe Connect update for CVE-2026-48360. It has different affected versions and fixes. Verify it independently if Connect is part of the environment. A Campaign closure report that says "Adobe patched" without naming the product and build can create a false assumption.&lt;/p&gt;

&lt;h2&gt;
  
  
  Define a defensible closure
&lt;/h2&gt;

&lt;p&gt;The remediation record should show the corrected Campaign build, successful service checks, the owner who verified the result, the date and time, and any remaining exceptions. It should also link the security bulletin and the asset ID. Add a follow-up check for standby systems and any deployment that missed the first window.&lt;/p&gt;

&lt;p&gt;CVE-2026-104350 is one part of a larger critical update. Verification is complete when the organization can show that Campaign Classic build 9403 is running on the intended systems, that the application functions, and that unknown or affected installations have a named owner and deadline. A ticket status alone does not answer those questions.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.adobe.com/trust/security/products/campaign/apsb26-162.html" rel="noopener noreferrer"&gt;Adobe APSB26-162&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.cve.org/CVERecord?id=CVE-2026-104350" rel="noopener noreferrer"&gt;CVE-2026-104350 record&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.adobe.com/trust/security/products/connect/apsb26-182.html" rel="noopener noreferrer"&gt;Adobe APSB26-182&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://securityonline.info/adobe-vulnerabilities-campaign-classic-connect/" rel="noopener noreferrer"&gt;Collected SecurityOnline source&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>adobecampaignclassic</category>
      <category>cve2026104350</category>
      <category>patchverification</category>
      <category>securityassurance</category>
    </item>
    <item>
      <title>Vitess VTAdmin: eleven title matches and an authentication layer you must design</title>
      <dc:creator>johnettagaweraks</dc:creator>
      <pubDate>Wed, 18 Nov 2026 13:20:48 +0000</pubDate>
      <link>https://dev.to/johnettagaweraks/vitess-vtadmin-eleven-title-matches-and-an-authentication-layer-you-must-design-27cf</link>
      <guid>https://dev.to/johnettagaweraks/vitess-vtadmin-eleven-title-matches-and-an-authentication-layer-you-must-design-27cf</guid>
      <description>&lt;h1&gt;
  
  
  Vitess VTAdmin: eleven title matches and an authentication layer you must design
&lt;/h1&gt;

&lt;p&gt;VTAdmin is the web and API layer for managing a Vitess deployment. It is not a single monolithic console with a built-in identity system. The Vitess documentation says authentication is obtained at the incoming HTTP and gRPC request boundary, authorization happens inside the &lt;code&gt;vtadmin.API&lt;/code&gt; layer, and deployment-specific authentication must be designed by the operator. There is no trust boundary between &lt;code&gt;vtadmin-web&lt;/code&gt; and &lt;code&gt;vtadmin-api&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;A count-only ZoomEye measurement on November 17, 2026 used &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and a page size of 1. &lt;code&gt;app="Vitess"&lt;/code&gt; returned 0. &lt;code&gt;title="VTAdmin"&lt;/code&gt; returned 11. The title matches are a small candidate set for a management surface whose protection depends heavily on the surrounding architecture.&lt;/p&gt;

&lt;p&gt;The phrase "no trust boundary" is not a vulnerability by itself. It is an architectural warning. The web client sends requests to the API, and the API must treat those requests according to the authentication and authorization policy. If the API is exposed directly, a proxy that protects the web page may not protect the management operations. If the API accepts requests from an internal network without authentication, an attacker who reaches that network can bypass the intended portal.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the counts can support
&lt;/h2&gt;

&lt;p&gt;Start an owned-asset review with the request path. Where does &lt;code&gt;vtadmin-web&lt;/code&gt; run? Where does &lt;code&gt;vtadmin-api&lt;/code&gt; listen? Which proxy or gateway sits in front of each? Is the API reachable from the same public host, a separate internal name, or a service mesh? Record the gRPC and HTTP endpoints separately. A title search may find only the web front end, while the API is the higher-value control plane.&lt;/p&gt;

&lt;p&gt;Vitess provides role-based access control at the API layer. The documentation discusses authentication plugins and authorisation decisions based on the actor and resource. An operator must connect the actor to a trusted identity source and write rules that match the actual operational roles. An RBAC system with a permissive default or an actor derived from an unverified header is not a security boundary.&lt;/p&gt;

&lt;p&gt;For each deployment, list the actors: human operators, CI jobs, monitoring systems, and support tools. Map each to the minimum API actions it needs. Review who can change keyspaces, shards, tablets, schema workflows, and topology records. Then verify that the API can distinguish those actors. A shared service account with broad authority makes incident attribution and least privilege difficult.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verification and next steps
&lt;/h2&gt;

&lt;p&gt;Network controls should reflect the control-plane role. Put VTAdmin behind an authenticated gateway or private management network. Restrict direct API access to expected proxy and operator networks. Use TLS for both browser and gRPC paths where the deployment supports it. Do not expose the API simply because the web client is served from the same hostname.&lt;/p&gt;

&lt;p&gt;Passive evidence can include the page title, server header, TLS certificate, and response behaviour. It cannot prove that the API is open or that RBAC is weak. Do not send management actions to unknown instances. For an owned instance, use configuration and approved test accounts to verify that unauthenticated requests fail and that a low-privilege actor cannot perform administrative operations.&lt;/p&gt;

&lt;p&gt;Logging should capture authentication results, the actor identity, the API resource and action, and the outcome. Correlate VTAdmin events with Vitess topology and schema changes. A missing actor field or a generic service identity makes an otherwise good authorisation decision hard to audit.&lt;/p&gt;

&lt;p&gt;The 11 title matches are small enough for a focused review. The 0 application result may reflect incomplete fingerprint coverage or a naming difference. Neither result is the answer to whether the API is protected. The answer comes from the operator-designed authentication boundary and the actual RBAC rules.&lt;/p&gt;

&lt;p&gt;VTAdmin is a useful control plane because it makes distributed Vitess operations visible. That same role makes it a high-value target. Inventory both web and API endpoints, attach them to a trusted identity source, and verify the path from browser to API. A management console without a clear trust boundary is an inventory gap waiting to become an incident.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://vitess.io/docs/24.0/reference/vtadmin/role-based-access-control/" rel="noopener noreferrer"&gt;Vitess VTAdmin role-based access control&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://vitess.io/docs/24.0/reference/vtadmin/operators_guide/" rel="noopener noreferrer"&gt;Vitess VTAdmin operator's guide&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>zoomeye</category>
      <category>zoom07</category>
    </item>
    <item>
      <title>Apache Polaris: four title matches and the identity boundary around a catalog API</title>
      <dc:creator>johnettagaweraks</dc:creator>
      <pubDate>Wed, 18 Nov 2026 10:01:16 +0000</pubDate>
      <link>https://dev.to/johnettagaweraks/apache-polaris-four-title-matches-and-the-identity-boundary-around-a-catalog-api-4h9c</link>
      <guid>https://dev.to/johnettagaweraks/apache-polaris-four-title-matches-and-the-identity-boundary-around-a-catalog-api-4h9c</guid>
      <description>&lt;h1&gt;
  
  
  Apache Polaris: four title matches and the identity boundary around a catalog API
&lt;/h1&gt;

&lt;p&gt;Apache Polaris is a catalog service for lakehouse data. A reachable Polaris endpoint may expose namespaces, tables, principals, roles, grants, and the management API used to change them. The security question is not whether a page says "Polaris" in its title. It is whether the catalog API is separated from the identities that can modify its security model.&lt;/p&gt;

&lt;p&gt;A count-only ZoomEye request on November 18, 2026 returned four matches for &lt;code&gt;title="Apache Polaris"&lt;/code&gt; and zero for &lt;code&gt;app="Apache Polaris"&lt;/code&gt;. The request used page 1, page size 1, and &lt;code&gt;sub_type=all&lt;/code&gt;. These are index observations, not four confirmed live catalogs and not four vulnerable systems. A title match can be a documentation page, a management console, or a stale response. A zero application-fingerprint count means the tested string did not classify an asset as that product.&lt;/p&gt;

&lt;p&gt;The official Polaris documentation describes authentication through an external OpenID Connect identity provider as well as an internal authentication system. The API accepts bearer tokens. The management API is separate from the catalog data path and includes operations for principal roles and grants. Polaris also supports an external policy decision point such as Open Policy Agent.&lt;/p&gt;

&lt;h2&gt;
  
  
  Identity is not authorization
&lt;/h2&gt;

&lt;p&gt;A valid token proves that an identity was issued by a trusted provider. It does not prove that the identity should be allowed to create a catalog, change a grant, or manage a principal. Polaris maps token claims to security roles and then applies catalog authorization. A deployment can therefore look correctly integrated with an identity provider while still granting too much authority to every authenticated user.&lt;/p&gt;

&lt;p&gt;The first inventory step is to identify the token issuer and audience. Check that production tokens are issued for the production Polaris API, not accepted from a broad internal issuer without audience restrictions. Review the &lt;code&gt;root&lt;/code&gt; principal and bootstrap credentials separately. The official guide describes using the bootstrap root token to create the initial principals and then avoiding root for ordinary API calls. If a deployment keeps using root for automation, the catalog has a single high-value identity with no useful separation.&lt;/p&gt;

&lt;p&gt;The second step is to map principals to catalog objects. A catalog may contain several schemas and tables with different owners. A principal role that can create objects in one catalog should not automatically manage principals or grants in another. Export the role assignments and compare them with the intended data domains. Test a low-privilege user against each management endpoint rather than reading a login page.&lt;/p&gt;

&lt;p&gt;The external policy decision point adds another boundary. A policy configuration that defaults to "none" for bearer authentication or uses an unreachable PDP can change how requests are evaluated. Policy changes should be versioned and tested in the same way as application code. The catalog should fail closed when an authorization decision cannot be made.&lt;/p&gt;

&lt;h2&gt;
  
  
  What four title matches do and do not establish
&lt;/h2&gt;

&lt;p&gt;Four matches are a small observation set, so the safest use is as a probe for further validation. For each match, verify the service, certificate, response body, and path. Look for &lt;code&gt;/api/catalog&lt;/code&gt; or management paths that answer without a 401 or 403. Do not send credentials to an unknown host and do not treat a login page as proof that the catalog API is protected.&lt;/p&gt;

&lt;p&gt;Use the count to ask an architecture question: do we know every catalog deployment in our estate? The public count is only a hint about how often the product name appears in indexed web content. Internal inventory, cloud resource lists, and Kubernetes discovery are more reliable for owned assets.&lt;/p&gt;

&lt;p&gt;The defensible conclusion is narrow. Polaris separates authentication from authorization and supports external identity and policy components, which gives operators useful controls. The risky condition is a deployment that treats a valid token as blanket permission or exposes a management API without a strong network boundary. The four title matches warrant a controlled inventory check, not a claim of compromise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Query evidence
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;title="Apache Polaris"
sub_type=all, page=1, pagesize=1, observed 2026-11-18T07:42:21+08:00, count=4
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://polaris.apache.org/in-dev/unreleased/managing-security/" rel="noopener noreferrer"&gt;Apache Polaris: Managing Security&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://polaris.apache.org/in-dev/unreleased/polaris-api-specs/" rel="noopener noreferrer"&gt;Apache Polaris: API Reference&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://polaris.apache.org/in-dev/unreleased/managing-security/external-pdp/" rel="noopener noreferrer"&gt;Apache Polaris: External Policy Decision Point&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.zoomeye.ai/searchResult?q=dGl0bGU9IkFwYWNoZSBQb2xhcmlzIg%3D%3D" rel="noopener noreferrer"&gt;ZoomEye count-only search for Apache Polaris&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>zoomeye</category>
      <category>apachepolaris</category>
      <category>catalog</category>
    </item>
    <item>
      <title>CAEP Turns Identity Changes into Access Events, but Consumers Must Enforce Them</title>
      <dc:creator>johnettagaweraks</dc:creator>
      <pubDate>Wed, 18 Nov 2026 07:25:17 +0000</pubDate>
      <link>https://dev.to/johnettagaweraks/caep-turns-identity-changes-into-access-events-but-consumers-must-enforce-them-afc</link>
      <guid>https://dev.to/johnettagaweraks/caep-turns-identity-changes-into-access-events-but-consumers-must-enforce-them-afc</guid>
      <description>&lt;h1&gt;
  
  
  CAEP Turns Identity Changes into Access Events, but Consumers Must Enforce Them
&lt;/h1&gt;

&lt;p&gt;Continuous Access Evaluation Profile 1.0 defines how cooperating providers send security events about a subject. The events can describe a session revocation, a credential change, a token revocation, an assurance-level change or another condition that should alter access. The profile is built on the Shared Signals Framework, so it combines event semantics with a delivery and subscription model.&lt;/p&gt;

&lt;p&gt;The first engineering mistake is to treat event delivery as authorization. A receiver that accepts an event without checking the issuer, signature, subject identifier and event type has created a new unauthenticated API. The second mistake is to accept the event and never apply it to a live session. A real CAEP deployment needs both a trustworthy event channel and a local policy that knows which resources must react.&lt;/p&gt;

&lt;h2&gt;
  
  
  The event is not the decision
&lt;/h2&gt;

&lt;p&gt;A transmitter may report that a user's session was revoked. The application should decide whether that revocation applies to its own session, its own token cache and its own high-risk operations. Session identifiers are deployment-specific. A subject identifier may be an email address in one provider and an opaque pairwise identifier in another. The receiver needs a mapping that is stable, auditable and resistant to account reuse.&lt;/p&gt;

&lt;p&gt;The event payload also has a timestamp, issuer and event type. These fields should be checked before the event reaches the authorization cache. A delayed event can be useful for investigation but may be too old to override a more recent authentication. A duplicate event should be idempotent. An event for an unknown subject should be quarantined, not silently applied to a similarly named user.&lt;/p&gt;

&lt;p&gt;CAEP is most valuable when the access decision is close to the resource. An API gateway can reject a new request after a revocation event. A long-lived background job may already be executing with a token that was valid when the job started. The design should define whether that job is interrupted, allowed to finish with an audit record, or required to reauthorize before its next high-risk action.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build the trust path before the dashboard
&lt;/h2&gt;

&lt;p&gt;The receiver should have a configured list of trusted transmitters, a key set, an accepted event schema and a maximum clock skew. It should verify signatures with a library that rejects algorithm changes and unknown key identifiers. It should authenticate the event source separately from the subject event. A signature that proves the payload came from a transmitter does not prove that the transmitter is authorized to make that claim.&lt;/p&gt;

&lt;p&gt;Subscriptions should be reviewed like any other privileged integration. Record which events are requested, which tenant or organization identifiers are in scope, who owns the subscription and how keys rotate. A test event can show that the pipe works, but it does not show that the receiver's policy is correct.&lt;/p&gt;

&lt;p&gt;Log the event identifier, issuer, type, subject mapping, receive time, verification result and action taken. Protect the subject identifiers and avoid copying raw identity claims into general-purpose analytics. Keep a separate audit trail for policy overrides, because the most important event is often the one an operator chose not to apply.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the worst moments
&lt;/h2&gt;

&lt;p&gt;Run failure tests during a credential reset, a device loss and a session invalidation. Confirm that a revoked session cannot start a new privileged operation, that a cached access token is invalidated within the stated window, and that an event from an unknown issuer is rejected. Then test a delayed or duplicated event. The system should not revoke an unrelated user or restore an authority that a later event removed.&lt;/p&gt;

&lt;p&gt;The profile gives identity providers and applications a common vocabulary for continuous evaluation. The organization still has to decide which decisions are continuous, which events can override which sessions and how quickly a local cache must converge. Those decisions belong in the access policy, not in the event feed.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://openid.net/specs/openid-caep-1_0-final.html" rel="noopener noreferrer"&gt;OpenID Continuous Access Evaluation Profile 1.0&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://openid.net/specs/openid-sharedsignals-framework-1_0-final.html" rel="noopener noreferrer"&gt;OpenID Shared Signals Framework 1.0&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>caep</category>
      <category>identity</category>
      <category>sharedsignals</category>
    </item>
    <item>
      <title>OpenVINO Model Server Has No Application Fingerprint and Twenty Broad Title Matches</title>
      <dc:creator>johnettagaweraks</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:21:37 +0000</pubDate>
      <link>https://dev.to/johnettagaweraks/openvino-model-server-has-no-application-fingerprint-and-twenty-broad-title-matches-4lfd</link>
      <guid>https://dev.to/johnettagaweraks/openvino-model-server-has-no-application-fingerprint-and-twenty-broad-title-matches-4lfd</guid>
      <description>&lt;h1&gt;
  
  
  OpenVINO Model Server Has No Application Fingerprint and Twenty Broad Title Matches
&lt;/h1&gt;

&lt;p&gt;OpenVINO Model Server serves machine-learning models through KServe-compatible gRPC and REST endpoints. It can run as a container or as a service, and its security model depends heavily on the deployment around it. The documentation states that the default container runs as a local account with UID 5000. It also states that the server does not currently provide access restrictions or traffic encryption on its gRPC and REST API endpoints.&lt;/p&gt;

&lt;p&gt;ZoomEye count-only queries on 2026-11-18 returned zero matches for &lt;code&gt;app="OpenVINO Model Server"&lt;/code&gt; and zero for &lt;code&gt;title="OpenVINO Model Server"&lt;/code&gt;. A shorter application query, &lt;code&gt;app="OpenVINO"&lt;/code&gt;, also returned zero. The broad title query &lt;code&gt;title="OpenVINO"&lt;/code&gt; returned 20. Those 20 matches are not a model-server census. They may include project pages, demos, documentation or applications that use the OpenVINO name without exposing the server API.&lt;/p&gt;

&lt;p&gt;The result is a useful example of fingerprint absence. A product can be present while ZoomEye has no stable application signature for the deployment. The absence of &lt;code&gt;app&lt;/code&gt; data should not become a statement that no instances are exposed. It means the query cannot support that conclusion.&lt;/p&gt;

&lt;h2&gt;
  
  
  The deployment must supply the missing control
&lt;/h2&gt;

&lt;p&gt;The documentation's security guidance is direct: restrict network access and use a reverse proxy or gateway when authentication or encryption is required. A deployment that publishes the REST or gRPC port to the internet without that layer has no product-level authentication to fall back on. The gateway should terminate TLS, authenticate clients and restrict which model endpoints are visible.&lt;/p&gt;

&lt;p&gt;Model content adds another concern. The server may load model files from a local directory or a remote repository. A model can contain custom code, pre- and post-processing logic or configuration that changes how input is handled. Treat model storage as a trusted supply-chain input. Do not let an unauthenticated client select an arbitrary repository path or model version.&lt;/p&gt;

&lt;p&gt;Container hardening should be part of the deployment template. The documented non-root UID is a useful default, but it does not replace a read-only model mount, a restrictive network policy or a resource limit. If a model needs a writable directory, give it a dedicated volume with a defined lifecycle. Do not run the container with additional capabilities unless the model or runtime produces a specific, tested requirement.&lt;/p&gt;

&lt;h2&gt;
  
  
  Look for the gateway, not the brand
&lt;/h2&gt;

&lt;p&gt;The practical inventory question is not only "where is OpenVINO?" It is "which HTTP and gRPC services are running inference and what protects them?" Search service inventories for OpenVINO base images, container names and model repository paths. Correlate those findings with Kubernetes ingress, service mesh policy and external DNS.&lt;/p&gt;

&lt;p&gt;For each deployment, record the model source, the network path, the TLS terminator, the authentication method and the identity used to call the model. Test an unauthenticated request from a network that should be denied. Test a request with a valid identity for a model the identity should not access. A successful inference call is the useful negative result here.&lt;/p&gt;

&lt;p&gt;The 20 broad title matches do not establish exposure. The official security guidance does establish the consequence of leaving the API unprotected. OpenVINO Model Server is best treated as an internal inference component with a gateway in front, not as a self-authenticating web application.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.openvino.ai/nightly/model-server/ovms_docs_security.html" rel="noopener noreferrer"&gt;OpenVINO Model Server security considerations&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.openvino.ai/2025/model-server/ovms_what_is_openvino_model_server.html" rel="noopener noreferrer"&gt;OpenVINO Model Server overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.openvino.ai/2024/openvino-workflow/model-server/ovms_extras_nginx-mtls-auth-readme.html" rel="noopener noreferrer"&gt;Securing OpenVINO Model Server with NGINX&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>zoomeye</category>
      <category>openvino</category>
      <category>modelserving</category>
    </item>
    <item>
      <title>Onyx AI at 102 title matches: API keys connect users, agents, and enterprise data</title>
      <dc:creator>johnettagaweraks</dc:creator>
      <pubDate>Wed, 18 Nov 2026 00:01:15 +0000</pubDate>
      <link>https://dev.to/johnettagaweraks/onyx-ai-at-102-title-matches-api-keys-connect-users-agents-and-enterprise-data-nia</link>
      <guid>https://dev.to/johnettagaweraks/onyx-ai-at-102-title-matches-api-keys-connect-users-agents-and-enterprise-data-nia</guid>
      <description>&lt;h1&gt;
  
  
  Onyx AI at 102 title matches: API keys connect users, agents, and enterprise data
&lt;/h1&gt;

&lt;p&gt;Onyx is an open-source enterprise search and AI assistant that can connect to internal documents, applications, and chat workflows. A self-hosted instance is more than a search page. It can hold connectors, user groups, model-provider credentials, API keys, agent definitions, and actions that call other services. The external exposure question should follow those identities.&lt;/p&gt;

&lt;p&gt;ZoomEye returned 102 matches for &lt;code&gt;title="Onyx AI"&lt;/code&gt; and zero for &lt;code&gt;app="Onyx AI"&lt;/code&gt; on November 18, 2026, using &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and page size 1. The count is an index observation. It may include product pages and unrelated content, and it does not show whether any host is a live or misconfigured deployment.&lt;/p&gt;

&lt;p&gt;Onyx's official developer page says the platform supports fine-grained API keys and APIs for messages, agents, LLMs, actions, and user authentication. Its product material describes permission-aware retrieval across connectors and support for self-hosted, cloud, or air-gapped deployment. Those features make identity integration central: the assistant has to decide which user can see which source, and which agent or API key can call which action.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three identities in one deployment
&lt;/h2&gt;

&lt;p&gt;The first identity is the human user. Group membership and source permissions determine which documents the assistant can retrieve. A public chat link or an unauthenticated search endpoint can bypass that model if it exposes results without the same authorization check.&lt;/p&gt;

&lt;p&gt;The second identity is the API key. A key may be scoped to a user, a service, or an integration. The important question is whether it inherits the creator's access or has a narrower purpose. An API key that can create agents, add connectors, or inspect messages has more authority than a read-only chat token. Inventory keys by owner, scope, creation date, and last use.&lt;/p&gt;

&lt;p&gt;The third identity is the agent or action. A connector may hold OAuth tokens for Drive, Slack, email, or another repository. An action may have access to a ticketing system or internal API. When a user asks the assistant to perform a task, the action should know whether it is acting for that user, as a shared service, or as an administrator. The presence of an LLM in the request path does not remove the need for object-level authorization.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to inspect on an owned instance
&lt;/h2&gt;

&lt;p&gt;Start from the application configuration and database, not from a title search. List users, groups, connectors, service accounts, API keys, agents, actions, and model providers. Check whether the deployment allows public signup or guest access. Review OAuth scopes and revoke connectors that no longer have an owner. Confirm that a low-privilege user cannot enumerate documents outside the connected source permissions.&lt;/p&gt;

&lt;p&gt;Test the API separately from the browser. A request with no token should receive an authentication error, not a generic page that reveals deployment details. A token for one user should not read another user's chat. A connector credential should not be reusable as a general API token. If the application supports administrative actions, require a distinct role and log the change.&lt;/p&gt;

&lt;p&gt;The language model provider adds another secret. A shared model key may be billed to the organization and may allow access to provider features that are not intended for every user. Use per-environment keys, spending limits, and rotation. Do not place the provider key in a prompt, a document, or a connector configuration that ordinary users can read.&lt;/p&gt;

&lt;h2&gt;
  
  
  Turning a broad count into a controlled check
&lt;/h2&gt;

&lt;p&gt;The exact title phrase is useful because it is specific, but it still cannot distinguish a legitimate public product page from an internal assistant. Before requesting any response body, verify that the host belongs to the organization. Respect scope and do not attempt authentication against systems you do not own. For owned hosts, compare the public endpoint with the internal inventory and the expected deployment mode.&lt;/p&gt;

&lt;p&gt;The result of the check should be a list of identities. Which human users can reach the assistant? Which keys can change its connectors? Which agents can call external tools? Which data sources trust the assistant as a user? A deployment that answers these questions has a meaningful security boundary around the product name.&lt;/p&gt;

&lt;p&gt;One hundred two title matches are small enough to review manually but large enough to show why automated classification can mislead. The product's value comes from joining systems together. Its risk comes from allowing one key or one agent to join them too broadly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Query evidence
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;title="Onyx AI"
sub_type=all, page=1, pagesize=1, observed 2026-11-18T07:42:27+08:00, count=102
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://onyx.app/developer-platform" rel="noopener noreferrer"&gt;Onyx developer platform&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://onyx.app/" rel="noopener noreferrer"&gt;Onyx product overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.zoomeye.ai/searchResult?q=dGl0bGU9Ik9ueXggQUki" rel="noopener noreferrer"&gt;ZoomEye count-only search for Onyx AI&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>zoomeye</category>
      <category>onyxai</category>
      <category>enterprisesearch</category>
    </item>
    <item>
      <title>The leaf CRL check that never runs in GoAhead</title>
      <dc:creator>johnettagaweraks</dc:creator>
      <pubDate>Tue, 17 Nov 2026 20:41:33 +0000</pubDate>
      <link>https://dev.to/johnettagaweraks/the-leaf-crl-check-that-never-runs-in-goahead-4dgk</link>
      <guid>https://dev.to/johnettagaweraks/the-leaf-crl-check-that-never-runs-in-goahead-4dgk</guid>
      <description>&lt;h1&gt;
  
  
  The leaf CRL check that never runs in GoAhead
&lt;/h1&gt;

&lt;h2&gt;
  
  
  Vulnerability overview
&lt;/h2&gt;

&lt;p&gt;CVE-2026-115881 is a precise certificate-state failure in GoAhead's OpenSSL implementation. The server loads a CRL but does not set the OpenSSL verification flag that makes the list effective. An affected mutual TLS service accepts a revoked client certificate. EmbedThis assigns CVSS 3.1 score 9.1 and fixes the issue in GoAhead 6.1.1.&lt;/p&gt;

&lt;p&gt;The affected versions are 3.4.5 through 6.1.0. The vendor maps the issue to CWE-295 and CWE-299. The first describes improper certificate validation; the second describes an improper check for certificate revocation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mechanism and exploitation conditions
&lt;/h2&gt;

&lt;p&gt;The relevant setting is &lt;code&gt;ME_GOAHEAD_SSL_REVOKE&lt;/code&gt;, which points to a PEM-encoded CRL. When the path is non-empty, GoAhead obtains the OpenSSL certificate store and calls &lt;code&gt;X509_STORE_load_locations&lt;/code&gt;. A failed load aborts startup, so the file-loading operation is not the missing step.&lt;/p&gt;

&lt;p&gt;The missing step is a call to enable &lt;code&gt;X509_V_FLAG_CRL_CHECK&lt;/code&gt;. OpenSSL's verifier checks the flag before it evaluates revocation. If neither CRL checking nor OCSP checking is enabled, the revocation routine returns success without consulting the list. The certificate can be listed as revoked and still pass.&lt;/p&gt;

&lt;p&gt;GoAhead's verification callback contains a default path that would reject &lt;code&gt;X509_V_ERR_CERT_REVOKED&lt;/code&gt;, but the verifier never produces that error. A valid chain with a good signature and a revoked leaf can therefore look successful to the callback.&lt;/p&gt;

&lt;p&gt;Exploitation requires the OpenSSL backend, &lt;code&gt;ME_GOAHEAD_SSL_VERIFY_PEER=1&lt;/code&gt;, a configured CA bundle, &lt;code&gt;ME_GOAHEAD_SSL_VERIFY_ISSUER=1&lt;/code&gt;, a non-empty CRL, and a revoked certificate from a trusted CA. The default build does not enable the first steps.&lt;/p&gt;

&lt;h2&gt;
  
  
  Impact
&lt;/h2&gt;

&lt;p&gt;The attacker receives the access attached to the certificate identity. If the certificate represented a field device, a support account, or an administrator endpoint, the application may expose management routes or operations that the operator believed had been revoked.&lt;/p&gt;

&lt;p&gt;The CVSS vector is network reachable, low complexity, no privileges, no user interaction, scope unchanged, with high confidentiality and integrity impact and no availability impact. It assumes the attacker already has the revoked certificate. The severity comes from the failure to enforce an expected access boundary.&lt;/p&gt;

&lt;h2&gt;
  
  
  Affected products and scope
&lt;/h2&gt;

&lt;p&gt;The defect is in GoAhead's OpenSSL integration. Mbedtls builds use a different revocation path and the vendor says they are not vulnerable to this CVE. GoAhead appears in many embedded management systems, so the product build and certificate configuration are more useful than a bare product name.&lt;/p&gt;

&lt;p&gt;The affected range is 3.4.5 through 6.1.0. Patching decisions should include the firmware version, the TLS backend, whether mutual TLS is required, the trusted CA bundle, issuer verification settings, and how the CRL is delivered and refreshed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Exposure context
&lt;/h2&gt;

&lt;p&gt;On November 18, 2026, ZoomEye returned 6,627,002 product-fingerprint matches for &lt;code&gt;app="GoAhead"&lt;/code&gt; and 0 matches for the exact CVE query. Exposure uses the larger successful product count, but that count does not show backend or certificate settings.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://www.zoomeye.ai/searchResult?q=YXBwPSJHb0FoZWFkIg%3D%3D" rel="noopener noreferrer"&gt;ZoomEye result&lt;/a&gt; should be treated as an inventory signal. It cannot establish that a device has a trusted CA bundle or a revoked client credential.&lt;/p&gt;

&lt;h2&gt;
  
  
  Remediation and mitigations
&lt;/h2&gt;

&lt;p&gt;Install GoAhead 6.1.1 or later. The fixed code enables leaf-certificate CRL checking after the list loads. The vendor deliberately leaves chain-wide checking disabled because it requires CRLs for every issuer in the trust chain.&lt;/p&gt;

&lt;p&gt;Until the fixed firmware is available, restrict access to the management service and review whether mutual TLS can be disabled safely. A network control can reduce reachability, but it does not repair the server's certificate decision.&lt;/p&gt;

&lt;p&gt;Test the patch with a certificate that the managed CA has revoked. Check for a failed handshake and the expected verification error. Also test a valid certificate to ensure the update did not break normal client authentication. The meaningful result is that the loaded CRL now participates in verification.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/embedthis/goahead/security/advisories/GHSA-5m75-xq69-c3c5" rel="noopener noreferrer"&gt;EmbedThis advisory GHSA-5m75-xq69-c3c5&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/embedthis/goahead/releases/tag/v6.1.1" rel="noopener noreferrer"&gt;GoAhead v6.1.1 release notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://foxio.io/blog/choose-your-backend-three-tls-bugs-in-goahead" rel="noopener noreferrer"&gt;FoxIO technical research&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.openwall.com/lists/oss-security/2026/10/28/1" rel="noopener noreferrer"&gt;oss-security disclosure&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>vulnerability</category>
      <category>goahead</category>
      <category>cve2026115881</category>
    </item>
    <item>
      <title>From scanner traffic to an interactive YOOtheme operator</title>
      <dc:creator>johnettagaweraks</dc:creator>
      <pubDate>Tue, 17 Nov 2026 17:20:55 +0000</pubDate>
      <link>https://dev.to/johnettagaweraks/from-scanner-traffic-to-an-interactive-yootheme-operator-ppm</link>
      <guid>https://dev.to/johnettagaweraks/from-scanner-traffic-to-an-interactive-yootheme-operator-ppm</guid>
      <description>&lt;h1&gt;
  
  
  From scanner traffic to an interactive YOOtheme operator
&lt;/h1&gt;

&lt;p&gt;The Unit 42 record for CVE-2026-102785 shows two stages that defenders often handle as separate events: automated exploitation and later hands-on activity. The sequence began with a scanner writing JPEG/PHP polyglot webshells to a WordPress uploads directory. Each drop was checked within seconds. About two minutes later, an interactive operator uploaded a fuller ALFA Team webshell and attempted to install gsocket.&lt;/p&gt;

&lt;p&gt;The vulnerability affects YOOtheme Pro 5.0.0 through 5.0.52 and is fixed in 5.0.53. Its image handler accepts a public signed image URL and insufficiently binds additional operations and the output destination to the signature. The attacker can therefore control file content and placement without authenticating to WordPress or Joomla.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the two-minute gap matters
&lt;/h2&gt;

&lt;p&gt;Fast validation indicates that the first stage was built for scale. A scanner can send many requests, check the result, and move on. The later operator step indicates that at least one successful drop was noticed and developed into broader access. The transition can happen faster than a daily vulnerability-management cycle.&lt;/p&gt;

&lt;p&gt;Logs need to preserve enough context to connect the stages. A scanner request may return HTTP 500 while still writing the file. The first-stage shell can then respond with a marker such as &lt;code&gt;WPCONFIG&lt;/code&gt; and accept commands through a query parameter. The operator may use different source addresses, so an IP-only pivot can split what should be one investigation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Evidence to correlate
&lt;/h2&gt;

&lt;p&gt;Start with the request URI. Look for &lt;code&gt;yootheme=cache/&lt;/code&gt;, &lt;code&gt;FromFile=php://input&lt;/code&gt;, and &lt;code&gt;Save=&lt;/code&gt; values ending in &lt;code&gt;.php&lt;/code&gt;. Include 500 responses. Correlate those times with new &lt;code&gt;yt[0-9a-f]{7}.php&lt;/code&gt; files and with execution by the web-server process.&lt;/p&gt;

&lt;p&gt;On Windows, process telemetry may show the web server spawning &lt;code&gt;cmd.exe /s /c&lt;/code&gt; for an &lt;code&gt;echo YTS...&lt;/code&gt; marker followed by &lt;code&gt;id&lt;/code&gt;. The operator later ran generic Linux commands despite the target being a Windows host, which Unit 42 interpreted as tooling aimed broadly at WordPress sites. The ALFA kit appeared under &lt;code&gt;wp-content/uploads/ALFA_DATA/alfacgiapi/&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Network telemetry may show the shell downloading a remote PHP loader or using &lt;code&gt;curl&lt;/code&gt; to fetch and run gsocket. Those events occur after the initial file write. If an endpoint solution blocks one step, the other steps can still provide evidence that the web shell executed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Containment without losing the trail
&lt;/h2&gt;

&lt;p&gt;When the request and execution evidence align, preserve the web log, process record, file, and payload hash. Isolate the host. Do not overwrite the uploads directory before capture. The affected application may be only the entry point, so review database access, administrator sessions, deployment secrets, and outbound connections from the same window.&lt;/p&gt;

&lt;p&gt;Updating YOOtheme Pro to 5.0.53 or later prevents new writes through this path. It does not invalidate a shell already on disk. If the server executed an attacker-controlled file, rebuild or restore from a clean backup and rotate every credential the web process could read.&lt;/p&gt;

&lt;h2&gt;
  
  
  Exposure context
&lt;/h2&gt;

&lt;p&gt;ZoomEye's &lt;code&gt;http.body="YOOtheme"&lt;/code&gt; search returned 34,682 pages, while the exact CVE filter returned zero. The product-string result is a broad inventory lead and not a count of vulnerable or compromised systems. It should be combined with version checks and endpoint evidence.&lt;/p&gt;

&lt;p&gt;The broader lesson is that exploitation timelines now overlap automated scanning and human follow-up. Detection for CVE-2026-102785 should not stop at a blocked request. It should look for the successful side effect, the validation command, and the later operator activity that turns a file write into a durable intrusion.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.cve.org/CVERecord?id=CVE-2026-102785" rel="noopener noreferrer"&gt;CVE record for CVE-2026-102785&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2026-102785" rel="noopener noreferrer"&gt;NVD entry for CVE-2026-102785&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://yootheme.com/changelog" rel="noopener noreferrer"&gt;YOOtheme Pro changelog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/PaloAltoNetworks/Unit42-timely-threat-intel/blob/main/2026-10-26-exploitation-of-CVE-2026-102785.txt" rel="noopener noreferrer"&gt;Unit 42 timely threat intelligence&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>vulnerability</category>
      <category>yoothemepro</category>
      <category>remotecodeexecution</category>
    </item>
    <item>
      <title>Jahia returned eight titles and no application matches, so the JCR and token paths lead</title>
      <dc:creator>johnettagaweraks</dc:creator>
      <pubDate>Tue, 17 Nov 2026 14:01:23 +0000</pubDate>
      <link>https://dev.to/johnettagaweraks/jahia-returned-eight-titles-and-no-application-matches-so-the-jcr-and-token-paths-lead-32h6</link>
      <guid>https://dev.to/johnettagaweraks/jahia-returned-eight-titles-and-no-application-matches-so-the-jcr-and-token-paths-lead-32h6</guid>
      <description>&lt;h1&gt;
  
  
  Jahia returned eight titles and no application matches, so the JCR and token paths lead
&lt;/h1&gt;

&lt;p&gt;Jahia is a Java content platform with site administration, server administration, a content repository, REST access, and optional personal API tokens. A small public title result can still identify a high-value deployment. The review should move from the page name to the repository and token paths that can change content or administer the server.&lt;/p&gt;

&lt;p&gt;On 2026-11-17, a bounded ZoomEye SDK query used &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and &lt;code&gt;pagesize=1&lt;/code&gt;. &lt;code&gt;app="Jahia"&lt;/code&gt; returned 0 total matches at 2026-11-17T06:55:11.495164+08:00. &lt;code&gt;title="Jahia"&lt;/code&gt; returned 8 total matches at 2026-11-17T06:55:12.681309+08:00. The observed total is shown by the &lt;a href="https://www.zoomeye.ai/searchResult?q=YXBwPSJKYWhpYSI%3D" rel="noopener noreferrer"&gt;application query&lt;/a&gt; and the &lt;a href="https://www.zoomeye.ai/searchResult?q=dGl0bGU9IkphaGlhIg%3D%3D" rel="noopener noreferrer"&gt;title query&lt;/a&gt;. The page size limited returned records, not the matched total.&lt;/p&gt;

&lt;p&gt;The app query returned zero and the title query returned eight. The small sample is manageable, but it is not an exhaustive count of Jahia deployments. A public host may use a custom title, a gateway, a headless front end, or an older registration. The zero application result should be stored with the title result and labelled as a field-specific observation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate site and server administration
&lt;/h2&gt;

&lt;p&gt;Jahia documentation separates site administration from server administration and describes roles that grant access to the backoffice and server configuration. A site editor should not inherit server-level module or user administration. The review should identify who can change roles, install modules, use the JCR API, and create personal API tokens.&lt;/p&gt;

&lt;p&gt;Personal API tokens are credentials that may work across a broad set of endpoints. The Jahia personal API tokens documentation describes restricted token-authentication URL patterns and permissions for token administration. A deployment should restrict token usage to the endpoints an integration needs, name the owner, and remove tokens when the owner leaves. A token created for a one-time migration should not remain as a permanent backoffice credential.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the content repository boundary
&lt;/h2&gt;

&lt;p&gt;The JCR API can reach content that the public site does not render. The same authentication session may work in a browser and in a REST call, which makes proxy and session policy important. A gateway that protects the backoffice HTML but leaves the JCR endpoint exposed has protected one representation of the same authority. Verify the route coverage, HTTP methods, authorization checks, and response handling for all content APIs.&lt;/p&gt;

&lt;p&gt;Also review module permissions. A module can add a workflow, a connector, or a custom endpoint that was not part of the core permission test. A public deployment with few visible pages can still have many internal sites or custom modules. The owner should provide that inventory.&lt;/p&gt;

&lt;h2&gt;
  
  
  Turn the title list into a bounded review
&lt;/h2&gt;

&lt;p&gt;For each title match, record host, title, certificate, owner, and expected deployment. Ask whether the host is a site, an authoring instance, a preview environment, or a shared platform. Do not test user credentials or token creation during external discovery. If the host is confirmed, review its role assignments and token list through an authorised administrative process.&lt;/p&gt;

&lt;p&gt;The query result can be reproduced by storing the exact dork, scope, count, and time. A later change from eight titles to a different number should be explained before it changes the asset ledger. A title change can be a rebrand, a login-page update, or a new deployment. It does not reveal which one without owner evidence.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep tokens out of the measurement
&lt;/h2&gt;

&lt;p&gt;Never paste a personal API token into a ZoomEye query or a public report. The index count does not need the secret. If a token is found in a public page or repository, treat it as a disclosure: identify the owning service, revoke it through the product, check its permission and usage, and preserve evidence for the incident process.&lt;/p&gt;

&lt;p&gt;Jahia's eight-title result is not a large population, but the assets may hold the site's content and administration path. Small counts make ownership review practical; they do not make the authority behind the host small.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;p&gt;[1] ZoomEye application query. &lt;a href="https://www.zoomeye.ai/searchResult?q=YXBwPSJKYWhpYSI%3D" rel="noopener noreferrer"&gt;https://www.zoomeye.ai/searchResult?q=YXBwPSJKYWhpYSI%3D&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;[2] ZoomEye title query. &lt;a href="https://www.zoomeye.ai/searchResult?q=dGl0bGU9IkphaGlhIg%3D%3D" rel="noopener noreferrer"&gt;https://www.zoomeye.ai/searchResult?q=dGl0bGU9IkphaGlhIg%3D%3D&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;[3] Jahia server administration. &lt;a href="https://academy.jahia.com/documentation/jahia-cms/jahia-8.2/system-administrator/administering-your-server/about-server-administration" rel="noopener noreferrer"&gt;https://academy.jahia.com/documentation/jahia-cms/jahia-8.2/system-administrator/administering-your-server/about-server-administration&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;[4] Jahia personal API token usage. &lt;a href="https://github.com/Jahia/personal-api-tokens/blob/main/docs/USAGE.md" rel="noopener noreferrer"&gt;https://github.com/Jahia/personal-api-tokens/blob/main/docs/USAGE.md&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>zoomeye</category>
      <category>assetinventory</category>
    </item>
    <item>
      <title>Shared compression dictionaries add cache and secret-dependent state</title>
      <dc:creator>johnettagaweraks</dc:creator>
      <pubDate>Tue, 17 Nov 2026 10:41:58 +0000</pubDate>
      <link>https://dev.to/johnettagaweraks/shared-compression-dictionaries-add-cache-and-secret-dependent-state-24gf</link>
      <guid>https://dev.to/johnettagaweraks/shared-compression-dictionaries-add-cache-and-secret-dependent-state-24gf</guid>
      <description>&lt;h1&gt;
  
  
  Shared compression dictionaries add cache and secret-dependent state
&lt;/h1&gt;

&lt;p&gt;Compression Dictionary Transport lets a server compress an HTTP response using a dictionary downloaded earlier. The browser can advertise a matching dictionary, the server can refer to a dictionary identifier, and both sides save bandwidth when a site serves many similar resources. The feature also adds a long-lived state object that affects encoding, caching, and information leakage.&lt;/p&gt;

&lt;p&gt;RFC 9842 defines the transport and its security considerations. The Risks are not limited to a broken decompressor. Shared dictionaries can make compression side channels easier to vary or repeat. If a response mixes attacker-controlled input with a secret, the compressed size can reveal information about the secret even when the dictionary itself contains only public data. The RFC recommends preventing active use of multiple dictionaries for the same content, disabling compression when any part of the content comes from an uncontrolled source, and protecting dictionary access with the same care as the response.&lt;/p&gt;

&lt;h2&gt;
  
  
  Same-origin restrictions are necessary
&lt;/h2&gt;

&lt;p&gt;Browser implementations restrict dictionaries to the same origin and tie dictionary-compressed resources to the document origin or a valid CORS path. The dictionary is also subject to cache partitioning. These restrictions reduce cross-origin reuse and tracking, but they do not remove the need for a server policy. A compromised same-origin resource can still influence what a user receives.&lt;/p&gt;

&lt;p&gt;The dictionary's URL, identifier, and matching rules should be treated as configuration, not optional performance metadata. A deployment that accepts a dictionary identifier from an untrusted request without checking its scope may let a client steer the server toward a stale or attacker-influenced object. The server should validate the exact identifier and match rule, and it should fail closed when the expected dictionary is unavailable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Plan versioning and rollback
&lt;/h2&gt;

&lt;p&gt;Use content hashes or monotonic versions for dictionary identity. Keep an old dictionary available until active clients have refreshed, then remove it through a controlled cache policy. Test a dictionary miss, a stale identifier, a corrupt payload, and a response where the encoded size differs from the stored metadata. A fast rollback should restore a known good dictionary without changing the response semantics.&lt;/p&gt;

&lt;p&gt;Because the feature is controlled by HTTP headers and sometimes HTML relationship attributes, review Content Security Policy and proxy rewriting rules. A dictionary request that is blocked by &lt;code&gt;connect-src&lt;/code&gt; or a gateway can produce a performance regression that looks like a network fault. Log the dictionary identifier and result, not the sensitive response content.&lt;/p&gt;

&lt;h2&gt;
  
  
  Do not compress mixed trust
&lt;/h2&gt;

&lt;p&gt;The most important rule is simple: do not combine secrets from one user with input chosen by another user in a dictionary-compressed response. If a template must mix public and private data, separate the response or disable dictionary compression for that route. Measure the benefit against the new state and side-channel surface. Compression is a transport optimization; it is not a reason to weaken a response boundary.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;p&gt;[1] RFC 9842, Compression Dictionary Transport. &lt;a href="https://datatracker.ietf.org/doc/rfc9842/" rel="noopener noreferrer"&gt;https://datatracker.ietf.org/doc/rfc9842/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;[2] MDN, Compression Dictionary Transport. &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Compression_dictionary_transport" rel="noopener noreferrer"&gt;https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Compression_dictionary_transport&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;[3] MDN, Use-As-Dictionary. &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Use-As-Dictionary" rel="noopener noreferrer"&gt;https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Use-As-Dictionary&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>http</category>
      <category>compression</category>
      <category>cache</category>
    </item>
  </channel>
</rss>
