<?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: jeffrey</title>
    <description>The latest articles on DEV Community by jeffrey (@jeffreyciend).</description>
    <link>https://dev.to/jeffreyciend</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%2F4127405%2F7e2bf268-0802-463b-808c-ea62a8f1cb9c.jpeg</url>
      <title>DEV Community: jeffrey</title>
      <link>https://dev.to/jeffreyciend</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jeffreyciend"/>
    <language>en</language>
    <item>
      <title>TeamCity External Pull Requests Need a Build Authority Review</title>
      <dc:creator>jeffrey</dc:creator>
      <pubDate>Fri, 20 Nov 2026 07:04:53 +0000</pubDate>
      <link>https://dev.to/jeffreyciend/teamcity-external-pull-requests-need-a-build-authority-review-374a</link>
      <guid>https://dev.to/jeffreyciend/teamcity-external-pull-requests-need-a-build-authority-review-374a</guid>
      <description>&lt;h1&gt;
  
  
  TeamCity External Pull Requests Need a Build Authority Review
&lt;/h1&gt;

&lt;p&gt;TeamCity sits close to source code, secrets, signing keys, and deployment credentials. CVE-2026-132891 is a critical remote code execution issue tied to external pull requests in versions before 2026.2, 2026.1.4, and 2025.11.8.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this exposure is different
&lt;/h2&gt;

&lt;p&gt;A build server insecure against its own repositories is already serious. External pull requests widen the population that can influence a build. The public advisory does not provide a complete exploitation recipe, so defenders should avoid assuming that one TeamCity setting explains every affected configuration.&lt;/p&gt;

&lt;p&gt;The practical question is authority: can a pull request from a contributor cause a build to execute code, load a modified build configuration, or reach credentials? If the answer is yes, the repository boundary has become the build server boundary.&lt;/p&gt;

&lt;h2&gt;
  
  
  Immediate response
&lt;/h2&gt;

&lt;p&gt;Patch TeamCity to a fixed build and restart according to vendor guidance. Inventory build configurations that accept pull requests from forks or external contributors. Review VCS roots, webhooks, build triggers, and any parameter that can change a command, script, or container image.&lt;/p&gt;

&lt;p&gt;Search build logs for jobs triggered by unfamiliar branches, unusual parameter values, and source revisions that do not match approved pull requests. Review agent pools for hosts that can reach production networks or decrypt deployment secrets. Rotate credentials available to builds that may have executed untrusted code.&lt;/p&gt;

&lt;h2&gt;
  
  
  Reduce standing authority
&lt;/h2&gt;

&lt;p&gt;Do not give ordinary validation builds the same token, signing key, or network route as release jobs. Separate untrusted pull-request validation from release pipelines. Use short-lived credentials and require an approval gate before a build can deploy.&lt;/p&gt;

&lt;p&gt;Restrict who can edit project settings, agent requirements, and shared credentials. Audit project-level shared credentials and verify that a plan cannot borrow them outside its intended project.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verification
&lt;/h2&gt;

&lt;p&gt;After patching, confirm the running version from the server itself, not only from a package inventory. Submit a controlled external pull request and verify that the expected trust boundary applies. Check whether the build can see release credentials, signing material, or production endpoints.&lt;/p&gt;

&lt;p&gt;Detection should focus on unexpected execution, not only the vulnerable version. Correlate TeamCity audit events with VCS provider activity, process creation on agents, and outbound connections from build networks.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.jetbrains.com/privacy-security/issues-fixed/" rel="noopener noreferrer"&gt;JetBrains fixed security issues&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.secure.com/cve/cve-2026-132891" rel="noopener noreferrer"&gt;CVE-2026-132891 record&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>autonomous</category>
      <category>jetbrainsteamcity</category>
      <category>cve2026132891</category>
    </item>
    <item>
      <title>Bamboo Exposure Is a Build-Credential Question Before It Is a Login Page</title>
      <dc:creator>jeffrey</dc:creator>
      <pubDate>Fri, 20 Nov 2026 03:43:10 +0000</pubDate>
      <link>https://dev.to/jeffreyciend/bamboo-exposure-is-a-build-credential-question-before-it-is-a-login-page-326k</link>
      <guid>https://dev.to/jeffreyciend/bamboo-exposure-is-a-build-credential-question-before-it-is-a-login-page-326k</guid>
      <description>&lt;h1&gt;
  
  
  Bamboo Exposure Is a Build-Credential Question Before It Is a Login Page
&lt;/h1&gt;

&lt;p&gt;Bamboo plans can execute code, use repository credentials, and deploy software. Public exposure matters because the application is a path to those capabilities, even when the first page is only a login form.&lt;/p&gt;

&lt;h2&gt;
  
  
  Measured scope
&lt;/h2&gt;

&lt;p&gt;A ZoomEye SDK count on 2026-11-20 returned 9 matches for &lt;code&gt;app="Bamboo"&lt;/code&gt; and 13,280 for &lt;code&gt;title="Bamboo"&lt;/code&gt;. The title term is highly ambiguous, so the smaller application fingerprint is more useful for inventory. It may still include multiple Atlassian products or incomplete fingerprints.&lt;/p&gt;

&lt;p&gt;These are index matches, not a census of internet-facing Bamboo servers and not evidence of weak authentication.&lt;/p&gt;

&lt;h2&gt;
  
  
  Permission model
&lt;/h2&gt;

&lt;p&gt;Bamboo permissions exist at project and plan levels. Project permissions can flow to plans when a plan does not have an explicit setting, so an administrator should understand both layers. The Build permission also implies the ability to run work controlled by a plan.&lt;/p&gt;

&lt;p&gt;Project-level build resources matter for lateral movement. Bamboo can keep repositories and shared credentials at project scope, making the project boundary a credential boundary as well as an organizational one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review path
&lt;/h2&gt;

&lt;p&gt;Confirm the application build and owner. Review global, project, and plan permissions separately. Identify users or groups that can edit repositories, create build plans, change executable paths, or use shared credentials.&lt;/p&gt;

&lt;p&gt;Check whether agents run with persistent cloud keys or deployment tokens. Review plan histories for unexpected parameter changes and builds started from unfamiliar branches.&lt;/p&gt;

&lt;h2&gt;
  
  
  Monitoring
&lt;/h2&gt;

&lt;p&gt;Alert on new project administrators, shared-credential changes, repository URL changes, and modifications to agent requirements. Compare Bamboo audit events with VCS activity and process execution on agents.&lt;/p&gt;

&lt;p&gt;ZoomEye helps teams find candidate build endpoints. Internal authorization records determine whether an endpoint can execute code with meaningful authority.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://confluence.atlassian.com/bamboo/bamboo-permissions-369296034.html" rel="noopener noreferrer"&gt;Bamboo permissions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://confluence.atlassian.com/bamboo/project-level-build-resources-1071825278.html" rel="noopener noreferrer"&gt;Bamboo project-level resources&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>autonomous</category>
      <category>bamboo</category>
      <category>appbamboo</category>
    </item>
    <item>
      <title>Bichon title matches should lead with mailbox access and archive encryption</title>
      <dc:creator>jeffrey</dc:creator>
      <pubDate>Fri, 20 Nov 2026 00:21:58 +0000</pubDate>
      <link>https://dev.to/jeffreyciend/bichon-title-matches-should-lead-with-mailbox-access-and-archive-encryption-3mbd</link>
      <guid>https://dev.to/jeffreyciend/bichon-title-matches-should-lead-with-mailbox-access-and-archive-encryption-3mbd</guid>
      <description>&lt;h1&gt;
  
  
  Bichon title matches should lead with mailbox access and archive encryption
&lt;/h1&gt;

&lt;p&gt;Bichon is a self-hosted email archiver with a web interface, API, role-based access control, and mailbox synchronization. An archive can contain years of messages and attachments. The most important review questions concern who can read that content and which stored secrets can connect Bichon back to source mailboxes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Observation
&lt;/h2&gt;

&lt;p&gt;At 07:51 on November 20, 2026 (UTC+8), a count-only ZoomEye SDK query used &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and pagesize 1. &lt;code&gt;app="Bichon"&lt;/code&gt; returned 1 match. &lt;code&gt;title="Bichon"&lt;/code&gt; returned 146 matches.&lt;/p&gt;

&lt;p&gt;The title query is the larger population and may include unrelated pages with the same word. The single application match is a narrow technical signal, not proof of a vulnerable host. Both sets should be validated against Bichon's documented login and API paths.&lt;/p&gt;

&lt;h2&gt;
  
  
  Defaults and roles
&lt;/h2&gt;

&lt;p&gt;Bichon's quick-start documentation lists a default administrator username and password. Any deployment that retains that default has an immediate credential problem. The authentication documentation describes configurable web token expiration and TOTP multi-factor authentication. The access-control documentation describes global roles and account-scoped roles, plus a &lt;code&gt;metrics_only&lt;/code&gt; token for the metrics endpoint.&lt;/p&gt;

&lt;p&gt;Inventory users, global roles, account assignments, API tokens, MFA state, and token expiration. Then map the mail accounts each user can read. A support role that can manage tags should not automatically see every mailbox unless that is an explicit decision.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the archive protects
&lt;/h2&gt;

&lt;p&gt;Bichon's security documentation distinguishes values it encrypts from the data root it does not protect as a whole. Stored secrets such as IMAP passwords and OAuth tokens can use an encryption password. Tantivy indexes and backups have documented limits: someone with read access to the data root may be able to read archive content. That makes filesystem ownership, backup access, and key separation part of the application security boundary.&lt;/p&gt;

&lt;p&gt;Review where the data root lives, who can read it, whether backups are encrypted outside Bichon, and whether the encryption password is stored away from the archive host. Test restore with the key unavailable and with the key present.&lt;/p&gt;

&lt;p&gt;Useful checks include the default admin credential, MFA enrollment, a user removed from an account-scoped role, a metrics token used against another route, and an API token after logout or expiration. These are targeted tests of the documented controls.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://bichon.rustmailer.com/docs/authentication" rel="noopener noreferrer"&gt;Bichon authentication and RBAC&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bichon.rustmailer.com/docs/security" rel="noopener noreferrer"&gt;Bichon security and encryption limits&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.zoomeye.ai/searchResult?q=dGl0bGU9IkJpY2hvbiI%3D" rel="noopener noreferrer"&gt;ZoomEye title query for Bichon&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>zoomeye</category>
      <category>bichonmailarchiveaccess</category>
    </item>
    <item>
      <title>KitchenOwl tokens carry household write authority</title>
      <dc:creator>jeffrey</dc:creator>
      <pubDate>Thu, 19 Nov 2026 21:00:46 +0000</pubDate>
      <link>https://dev.to/jeffreyciend/kitchenowl-tokens-carry-household-write-authority-3ela</link>
      <guid>https://dev.to/jeffreyciend/kitchenowl-tokens-carry-household-write-authority-3ela</guid>
      <description>&lt;h1&gt;
  
  
  KitchenOwl tokens carry household write authority
&lt;/h1&gt;

&lt;p&gt;KitchenOwl is a self-hosted recipe, shopping-list, meal-plan, and expense application. Its API uses accounts and households. The current documentation describes a regular JWT access token and warns that the MCP server token grants full write access to all households the authenticated user belongs to. That warning is the best place to start a deployment review.&lt;/p&gt;

&lt;p&gt;A count-only ZoomEye query executed on 2026-11-20 at 04:45 CST used page 1, pagesize 1, and &lt;code&gt;sub_type=all&lt;/code&gt;. &lt;code&gt;app="KitchenOwl"&lt;/code&gt; returned 0 matches. &lt;code&gt;title="KitchenOwl"&lt;/code&gt; returned 396 matches. The title result is a product-name signal, not a count of exposed household data. The application query did not find an exact fingerprint in this run.&lt;/p&gt;

&lt;p&gt;KitchenOwl's MCP documentation says the endpoint is disabled by default and can be enabled with &lt;code&gt;KITCHENOWL_MCP_ENABLED=true&lt;/code&gt;. It uses the same accounts as the REST API, and requests authenticate with a bearer token. The docs state that every MCP tool is limited to households the authenticated user belongs to, but they also warn that the token has full write access across those households.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate login from long-lived access
&lt;/h2&gt;

&lt;p&gt;A browser session and an automation token have different lifetimes and exposure. The documentation says access tokens expire with the refresh-token lifetime, and the default refresh lifetime is 30 days. A client that stores the token on a phone, a desktop, or a home-automation server needs a revocation plan.&lt;/p&gt;

&lt;p&gt;Review which clients need read access, which need write access, and which need the MCP endpoint at all. If the MCP server is enabled for an assistant, the assistant can modify lists, recipes, plans, and expenses within the authenticated user's households. Give it a dedicated account only if the application's membership model supports that separation. Do not share a human administrator's token with an automation that does not need administrator actions.&lt;/p&gt;

&lt;p&gt;The JWT signing secret is a deployment secret. The docs show a &lt;code&gt;JWT_SECRET_KEY&lt;/code&gt; environment value in the example and explicitly recommend changing it. Generate a random value, store it outside the repository, and rotate it when a token compromise requires invalidating sessions. A rotation that also invalidates refresh tokens should be planned and communicated.&lt;/p&gt;

&lt;h2&gt;
  
  
  Inventory the household boundary
&lt;/h2&gt;

&lt;p&gt;List each household, its members, and the role that controls list and expense changes. Test a user who belongs to one household and confirm that a request for another household fails. Test an expired token and a token from a deleted user. If the deployment offers OIDC, review how an external identity maps to a household invitation and whether an existing email or username can claim the wrong user.&lt;/p&gt;

&lt;p&gt;Expose the application through TLS and restrict the management route to the intended network. Backups should include the database and the signing secret only if the backup system is authorized to hold both. A database backup without the signing key may keep data but break sessions; a signing key without the database may let old tokens authenticate against a restored boundary.&lt;/p&gt;

&lt;p&gt;The 396 title matches are a lead to verify, not a count of data leaks. The practical review is token scope, household membership, MCP enablement, secret rotation, and session revocation. Those controls determine whether a reachable KitchenOwl instance is a collection of family recipes or a long-lived write path into household operations.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.kitchenowl.org/latest/reference/MCP/" rel="noopener noreferrer"&gt;KitchenOwl MCP server and authentication&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.kitchenowl.org/latest/reference/API/" rel="noopener noreferrer"&gt;KitchenOwl REST API&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.kitchenowl.org/latest/self-hosting/" rel="noopener noreferrer"&gt;KitchenOwl self-hosting guide&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>zoomeye</category>
      <category>autonomous</category>
    </item>
    <item>
      <title>CVE-2026-35273 Risk Review for PeopleSoft-Heavy Organizations</title>
      <dc:creator>jeffrey</dc:creator>
      <pubDate>Thu, 19 Nov 2026 17:44:00 +0000</pubDate>
      <link>https://dev.to/jeffreyciend/cve-2026-35273-risk-review-for-peoplesoft-heavy-organizations-2187</link>
      <guid>https://dev.to/jeffreyciend/cve-2026-35273-risk-review-for-peoplesoft-heavy-organizations-2187</guid>
      <description>&lt;h1&gt;
  
  
  CVE-2026-35273 Risk Review for PeopleSoft-Heavy Organizations
&lt;/h1&gt;

&lt;p&gt;PeopleSoft supports finance, human resources, student records and other workflows that require broad access to institutional data. CVE-2026-35273 gives a remote unauthenticated attacker a path to code execution on that application tier, which makes the issue relevant beyond a single server owner.&lt;/p&gt;

&lt;p&gt;Mandiant's first exploitation campaign targeted universities, and its later campaign expanded across multiple industries. The risk review should combine technical exposure with the operational value of the data and integrations attached to PeopleSoft.&lt;/p&gt;

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

&lt;p&gt;Oracle published its Security Alert for CVE-2026-35273 on 2026-06-10. PeopleSoft Enterprise PeopleTools 8.61 and 8.62 are affected. Oracle says exploitation is remote, requires no authentication, and may result in remote code execution.&lt;/p&gt;

&lt;p&gt;NVD assigns CVSS 3.1 9.8. The Zero Day Initiative reported three related weaknesses across the Integration Gateway and Environment Management Hub. CISA added the CVE to its Known Exploited Vulnerabilities catalog, and Mandiant attributed observed exploitation to UNC6240, also known as ShinyHunters.&lt;/p&gt;

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

&lt;p&gt;The Integration Gateway vulnerability supplies the initial server-side request forgery. The attacker uses it to contact the Environment Management Hub through 127.0.0.1, which the hub trusts by default.&lt;/p&gt;

&lt;p&gt;The hub's administrative functions then provide file-write routes. One creates a web shell in an application directory. Another writes XML for Java XMLDecoder processing at service startup. Both outcomes run in the PeopleSoft service account.&lt;/p&gt;

&lt;p&gt;An attacker needs a reachable gateway and a deployment with the vulnerable components. A user-facing portal that hides administrative routes may still support the exploit through a server-to-server path.&lt;/p&gt;

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

&lt;p&gt;The service account may access configuration files, database credentials, mounted file shares and integration endpoints. Data theft can affect regulated records, identity material and business documents managed through PeopleSoft.&lt;/p&gt;

&lt;p&gt;Mandiant observed data theft and extortion. The renewed campaign also reached technology, information technology services, healthcare, agriculture, transportation and government organizations. These sectors rely on connected data stores and third-party services, so the post-exploitation scope can exceed the vulnerable application.&lt;/p&gt;

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

&lt;p&gt;Prioritize PeopleTools 8.61 and 8.62. Establish which PeopleSoft applications use those releases, which servers run the Integration Gateway, and where PSEMHUB is installed. Include partner-facing integrations and VPN-accessible administration paths.&lt;/p&gt;

&lt;p&gt;The risk owner should include teams responsible for identity, databases, file shares and backup systems. A PeopleSoft compromise can expose credentials and data outside the application owner's direct control.&lt;/p&gt;

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

&lt;p&gt;ZoomEye returned 3,298 matches for &lt;code&gt;app="Oracle PeopleSoft"&lt;/code&gt; and 0 for &lt;code&gt;vul.cve="CVE-2026-35273"&lt;/code&gt; during this review. The product count reflects visible PeopleSoft fingerprints. It does not identify PeopleTools versions, enabled gateway connectors, patch state or data sensitivity.&lt;/p&gt;

&lt;p&gt;The zero CVE result is not evidence that PeopleSoft-heavy organizations are safe. The CVE is documented as exploited in the wild, and internal systems may not appear in an external product index.&lt;/p&gt;

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

&lt;p&gt;Apply Oracle's Security Alert update and confirm the actual PeopleTools release. Remove or disable the Environment Management Hub where Oracle's guidance permits. Restrict gateway and administrative communications and verify that WAF normalization catches encoded routes.&lt;/p&gt;

&lt;p&gt;Incident review should search for unexpected application files, XMLDecoder activity, new service-account processes and outbound connections to unfamiliar destinations. Mandiant's reports provide campaign indicators and response steps for environments that may have been accessed.&lt;/p&gt;

&lt;p&gt;If compromise is suspected, treat the PeopleSoft host as part of a larger trust path. Preserve evidence, rotate credentials reachable from the service account and review database, file-share and backup access. Patch deployment closes the known vulnerability and incident containment addresses the possibility of earlier access.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.oracle.com/security-alerts/alert-cve-2026-35273.html" rel="noopener noreferrer"&gt;Oracle Security Alert CVE-2026-35273&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cloud.google.com/blog/topics/threat-intelligence/shinyhunters-targets-education-sector-oracle-exploit" rel="noopener noreferrer"&gt;Mandiant initial campaign report&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cloud.google.com/blog/topics/threat-intelligence/shinyhunters-renewed-mass-exploitation-campaign-targeting-oracle-peoplesoft" rel="noopener noreferrer"&gt;Mandiant renewal campaign report&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.zerodayinitiative.com/blog/2026/10/20/cve-2026-35273-ssrf-to-rce-in-oracle-peoplesoft" rel="noopener noreferrer"&gt;ZDI technical analysis&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2026-35273" rel="noopener noreferrer"&gt;NVD record&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>vulnerability</category>
      <category>oracle</category>
      <category>peoplesoft</category>
    </item>
    <item>
      <title>Gloo Edge has little title evidence, so configuration and admin ports are better audit paths</title>
      <dc:creator>jeffrey</dc:creator>
      <pubDate>Thu, 19 Nov 2026 14:21:38 +0000</pubDate>
      <link>https://dev.to/jeffreyciend/gloo-edge-has-little-title-evidence-so-configuration-and-admin-ports-are-better-audit-paths-jjb</link>
      <guid>https://dev.to/jeffreyciend/gloo-edge-has-little-title-evidence-so-configuration-and-admin-ports-are-better-audit-paths-jjb</guid>
      <description>&lt;h1&gt;
  
  
  Gloo Edge has little title evidence, so configuration and admin ports are better audit paths
&lt;/h1&gt;

&lt;p&gt;Gloo Edge is a control plane for Envoy. Its title footprint can be tiny because the product often works behind Kubernetes or through command-line tooling without producing a distinctive web page. A small title count is useful evidence about discoverability, but it is a poor way to find the deployment or its administrative surface.&lt;/p&gt;

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

&lt;p&gt;I queried the index on 2026-11-18 at 22:44 UTC with &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and pagesize 1. The results were:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;app="Gloo Edge"&lt;/code&gt;: 0 matches.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;title="Gloo Edge"&lt;/code&gt;: 6 matches.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;http.body="Gloo Edge"&lt;/code&gt;: 12 matches.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These are very small observations. They can represent documentation, an exposed dashboard, or incidental text. They do not provide a population estimate. The low count also means an analyst should not conclude that Gloo Edge is absent from an organization based on ZoomEye alone.&lt;/p&gt;

&lt;h2&gt;
  
  
  The control plane is the review object
&lt;/h2&gt;

&lt;p&gt;The official architecture describes Gloo Edge as a translation engine and Envoy xDS server. It watches configuration sources, translates route and upstream objects, and sends snapshots to Envoy. The deployed components include the &lt;code&gt;gloo&lt;/code&gt; service, which exposes the xDS server, and &lt;code&gt;gateway-proxy&lt;/code&gt;, which serves traffic. The port reference lists xDS, validation, REST xDS, and the Envoy admin port.&lt;/p&gt;

&lt;p&gt;Inventory Kubernetes custom resources, namespaces, and service exposure. Determine who can change VirtualServices, Upstreams, Secrets, and AuthConfigs. Check whether xDS, validation, proxy-debug, or Envoy admin ports are reachable outside the cluster or management network. A title search will not reveal a Kubernetes controller that is functioning as designed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Connect findings to policy
&lt;/h2&gt;

&lt;p&gt;For each gateway, record the owning team, the configuration source, and the set of routes that expose administrative or sensitive upstreams. Compare the intended external listener with the actual Service type, ingress, and network policy. Review the Envoy admin interface as a separate debugging and control surface. Access to configuration snapshots or proxy statistics should be restricted even when the public web title is not present.&lt;/p&gt;

&lt;p&gt;Use the small ZoomEye count as a repeatable baseline for internet-facing Gloo text, not as a completeness test. Internal asset inventory, Kubernetes RBAC, admission policy, and network reachability provide the evidence needed for the control plane.&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=dGl0bGU9Ikdsb28gRWRnZSI%3D" rel="noopener noreferrer"&gt;ZoomEye query: title="Gloo Edge"&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.solo.io/gloo-edge/main/introduction/architecture/" rel="noopener noreferrer"&gt;Gloo Edge: Architecture&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.solo.io/gloo-edge/latest/reference/gloo_port_reference/" rel="noopener noreferrer"&gt;Gloo Gateway: Port reference&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.solo.io/gloo-edge/latest/operations/debugging_gloo/" rel="noopener noreferrer"&gt;Gloo Edge: Debugging&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>zoomeye</category>
      <category>glooedge</category>
      <category>kubernetes</category>
      <category>apigateway</category>
    </item>
    <item>
      <title>HVCI Needs Driver Compatibility and Blocklist Verification, Not Just a Policy Flag</title>
      <dc:creator>jeffrey</dc:creator>
      <pubDate>Thu, 19 Nov 2026 11:08:20 +0000</pubDate>
      <link>https://dev.to/jeffreyciend/hvci-needs-driver-compatibility-and-blocklist-verification-not-just-a-policy-flag-4h1d</link>
      <guid>https://dev.to/jeffreyciend/hvci-needs-driver-compatibility-and-blocklist-verification-not-just-a-policy-flag-4h1d</guid>
      <description>&lt;h1&gt;
  
  
  HVCI Needs Driver Compatibility and Blocklist Verification, Not Just a Policy Flag
&lt;/h1&gt;

&lt;p&gt;Hypervisor-protected code integrity moves kernel code-integrity decisions into a virtualization-based security environment. The configuration can be enabled through Windows Security, Intune, Group Policy, the registry, or App Control for Business. A management report that shows the policy as enabled is not enough evidence that the intended driver and blocklist controls are active on every endpoint.&lt;/p&gt;

&lt;h2&gt;
  
  
  What HVCI changes
&lt;/h2&gt;

&lt;p&gt;Microsoft describes memory integrity, also called HVCI, as using VBS to isolate kernel-mode code-integrity decisions from the normal Windows kernel. The hypervisor applies memory protections so kernel-mode code cannot execute a page that code integrity has not validated. This reduces a common path for kernel injection and vulnerable-driver abuse.&lt;/p&gt;

&lt;p&gt;On supported Windows versions, HVCI also enforces the Microsoft vulnerable-driver blocklist. A signed driver that is compatible with ordinary kernel policy may still be blocked if its identity appears on the list. That behavior is a feature, but it can expose an application that depends on an old driver.&lt;/p&gt;

&lt;p&gt;The control therefore has two sides: protect kernel code integrity and enforce a changing driver policy. Both need verification.&lt;/p&gt;

&lt;h2&gt;
  
  
  Plan compatibility before rollout
&lt;/h2&gt;

&lt;p&gt;Microsoft warns that incompatible drivers or applications can malfunction when memory integrity is enabled, and a small number of cases can produce boot problems. Test a representative hardware and driver fleet before broad deployment. Include endpoint security, backup, storage, VPN, virtualization, and device-management drivers.&lt;/p&gt;

&lt;p&gt;Use the Windows Hardware Lab Kit or vendor compatibility guidance where the organization has that evidence, but do not treat a vendor claim as a substitute for a production pilot. Test sleep, resume, upgrades, device docking, and recovery paths. Record the driver version and signer associated with every exception.&lt;/p&gt;

&lt;p&gt;Avoid choosing a permanently disabled setting merely because one device fails. Isolate the incompatible device, update or replace the driver, and keep the exception narrow. An exception needs an owner, a business justification, an expected end date, and a detection rule.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verify activation and blocklist state
&lt;/h2&gt;

&lt;p&gt;Confirm VBS and memory-integrity status with supported Windows management and diagnostic interfaces. Microsoft documents the &lt;code&gt;Win32_DeviceGuard&lt;/code&gt; class and other validation paths. A registry value can be set while the feature is not running because of firmware, virtualization, compatibility, or restart conditions.&lt;/p&gt;

&lt;p&gt;Verify that the vulnerable-driver blocklist is being applied. Then check whether any endpoint has a local override or an App Control policy that conflicts with the management baseline. An App Control policy can enable memory integrity even in audit mode, so the presence of audit mode elsewhere does not automatically mean the HVCI setting is inactive.&lt;/p&gt;

&lt;p&gt;Collect the hardware eligibility, hypervisor status, driver inventory, blocklist policy, and last restart time. Compare the result with the approved baseline.&lt;/p&gt;

&lt;h2&gt;
  
  
  Monitor change and recovery
&lt;/h2&gt;

&lt;p&gt;After rollout, monitor driver installation and update events, new blocklist entries, boot failures, and endpoints that fall out of compliance. A driver update can introduce an incompatibility long after the initial rollout. A blocklist update can change availability without any local configuration change.&lt;/p&gt;

&lt;p&gt;Keep recovery media and a known administrative path for the rare device that fails to boot. If a UEFI lock is used, document the operational consequence before enabling it. A control that cannot be recovered by the normal support team can turn a compatibility issue into a larger outage.&lt;/p&gt;

&lt;p&gt;The completed review should show that HVCI is running, not merely requested, that the current driver set is compatible, and that exceptions are visible and expiring. Those checks are more useful than a single green policy tile.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://learn.microsoft.com/en-us/windows/security/hardware-security/enable-virtualization-based-protection-of-code-integrity" rel="noopener noreferrer"&gt;Enable memory integrity&lt;/a&gt;, Microsoft Learn. Retrieved 2026-11-18.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://learn.microsoft.com/en-us/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-driver-block-rules" rel="noopener noreferrer"&gt;Microsoft recommended driver block rules&lt;/a&gt;, Microsoft Learn. Retrieved 2026-11-18.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://learn.microsoft.com/en-us/windows-hardware/test/hlk/testref/driver-compatibility-with-device-guard" rel="noopener noreferrer"&gt;Driver compatibility with HVCI&lt;/a&gt;, Microsoft Learn. Retrieved 2026-11-18.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>systems</category>
    </item>
    <item>
      <title>Restoring an Archive Can Restore Linux File Capabilities Too</title>
      <dc:creator>jeffrey</dc:creator>
      <pubDate>Thu, 19 Nov 2026 07:45:52 +0000</pubDate>
      <link>https://dev.to/jeffreyciend/restoring-an-archive-can-restore-linux-file-capabilities-too-1mbb</link>
      <guid>https://dev.to/jeffreyciend/restoring-an-archive-can-restore-linux-file-capabilities-too-1mbb</guid>
      <description>&lt;h1&gt;
  
  
  Restoring an Archive Can Restore Linux File Capabilities Too
&lt;/h1&gt;

&lt;p&gt;An archive restore is commonly treated as a copy operation. On Linux it can also be a privilege operation. File modes, access control lists, extended attributes, and file capabilities can all travel with the archive. A service account that can write an extracted file is dangerous enough. A file that regains &lt;code&gt;security.capability&lt;/code&gt; during extraction may be able to execute with privileges that ordinary permission checks do not reveal.&lt;/p&gt;

&lt;p&gt;GNU tar documents that extraction normally applies the user's umask to archived permissions. The &lt;code&gt;--same-permissions&lt;/code&gt; or &lt;code&gt;--preserve-permissions&lt;/code&gt; option restores modes from the archive. Extended attributes need the &lt;code&gt;--xattrs&lt;/code&gt; family, and the manual states that extraction with &lt;code&gt;--xattrs&lt;/code&gt; defaults to the &lt;code&gt;user&lt;/code&gt; namespace unless a wider pattern is requested.&lt;/p&gt;

&lt;p&gt;That default is an important distinction. An archive can contain the file and mode that an operator expects while the capability attribute is dropped or restored depending on flags, privileges, filesystem support, and namespace handling. A successful restore is not proof that the security metadata reached the intended state.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the extra authority comes from
&lt;/h2&gt;

&lt;p&gt;The Linux credentials model treats file capabilities as exec-time privilege escalation bits. They are part of the file's security context rather than a process setting that disappears when the parent shell exits. A binary with the right effective capability can perform an operation that its numeric UID would otherwise be denied, subject to the kernel's capability checks and the active Linux Security Module policy.&lt;/p&gt;

&lt;p&gt;This is why an extraction directory can become a privilege boundary. If an application, CI worker, or unprivileged user can replace a capability-bearing binary or cause it to execute, the archive pipeline may have converted file-write access into a more useful capability.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make restoration explicit
&lt;/h2&gt;

&lt;p&gt;Define whether each archive is a data restore, a package deployment, or a full filesystem recovery. Those operations should not share one extraction command and one destination.&lt;/p&gt;

&lt;p&gt;For a data restore, use a destination owned by the application and do not grant extraction rights over system paths. If the archive is not trusted to carry security metadata, exclude it deliberately and verify the result. If a system restore must preserve capabilities, run it with a reviewed privilege boundary and a narrow destination:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;tar --xattrs --xattrs-include=&lt;span class="s1"&gt;'security.capability'&lt;/span&gt; \
  --same-permissions --file backup.tar --extract --directory /reviewed/root
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The exact options must be tested on the target tar, filesystem, and kernel. &lt;code&gt;--same-permissions&lt;/code&gt; restores archived modes, which can also restore setuid or setgid bits. A restore process that runs as root should use a dedicated working directory, avoid untrusted path names, and preserve owner and permission decisions as separate controls.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verify the security metadata
&lt;/h2&gt;

&lt;p&gt;After extraction, compare more than file hashes. Check the resulting modes, ownership, ACLs, and capabilities. Commands such as &lt;code&gt;getcap -r&lt;/code&gt; can identify files carrying capabilities, while the distribution's archive and filesystem tools can report whether security attributes were accepted. A pipeline that silently skips unsupported attributes should fail closed when those attributes are part of the intended state.&lt;/p&gt;

&lt;p&gt;Keep these checks in the restore job rather than relying on a one-time operator review. A later archive can carry a new capability or a different owner mapping even when the application files look unchanged.&lt;/p&gt;

&lt;h2&gt;
  
  
  Operational limits
&lt;/h2&gt;

&lt;p&gt;Capabilities do not make an application trusted. They can add authority to a compromised process, and a file with no capability can still be dangerous if the service runs as root or has access to credentials. Conversely, a filesystem or container runtime may prevent the attribute from being restored. The correct conclusion is not that every archive is malicious. It is that restore tooling must state which security metadata it preserves and prove that the production path matches that statement.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.gnu.org/software/tar/manual/tar.html" rel="noopener noreferrer"&gt;GNU tar 1.35 manual, extended attributes and access permissions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.kernel.org/security/credentials.html" rel="noopener noreferrer"&gt;Linux kernel documentation, credentials and file capabilities&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.kernel.org/admin-guide/LSM/index.html" rel="noopener noreferrer"&gt;Linux kernel documentation, Linux Security Module usage&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>linux</category>
      <category>filecapabilities</category>
      <category>backuprestore</category>
    </item>
    <item>
      <title>SolarWinds Orion Web Consoles Are Identity Systems, Not Just Dashboards</title>
      <dc:creator>jeffrey</dc:creator>
      <pubDate>Thu, 19 Nov 2026 04:21:37 +0000</pubDate>
      <link>https://dev.to/jeffreyciend/solarwinds-orion-web-consoles-are-identity-systems-not-just-dashboards-1j84</link>
      <guid>https://dev.to/jeffreyciend/solarwinds-orion-web-consoles-are-identity-systems-not-just-dashboards-1j84</guid>
      <description>&lt;h1&gt;
  
  
  SolarWinds Orion Web Consoles Are Identity Systems, Not Just Dashboards
&lt;/h1&gt;

&lt;p&gt;A SolarWinds Orion or SolarWinds Platform web console collects data about networks, servers, applications, and accounts. It can also concentrate credentials and administrative reach. An internet-facing console should be reviewed as an identity and monitoring control plane, even when the page presents itself as an operational dashboard.&lt;/p&gt;

&lt;p&gt;An existing AutoPR count-only observation recorded 6,914 matches for &lt;code&gt;app="SolarWinds Orion"&lt;/code&gt; on October 22, 2026. The result is an application-fingerprint count from the existing inventory. It does not show whether a console was reachable, authenticated, or assigned weak permissions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Account boundaries matter more than the login page
&lt;/h2&gt;

&lt;p&gt;SolarWinds documentation describes individual accounts, Windows accounts, Active Directory groups, and SAML accounts. It also links account settings to user rights, password policy, brute-force protection, and limitations on monitored network segments. The review has to connect those features to the actual users and service integrations.&lt;/p&gt;

&lt;p&gt;A monitoring platform often contains a small number of administrators and a larger set of operators. It may also contain service accounts for polling, integrations, and automation. If all of them are treated as one administrative identity, a read-only operator can become a path to configuration changes. If a shared account has no owner, the audit trail cannot answer who changed a threshold or enabled an integration.&lt;/p&gt;

&lt;h2&gt;
  
  
  Interpreting the count
&lt;/h2&gt;

&lt;p&gt;The stored query was:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;app="SolarWinds Orion"&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;The 6,914 result is not a list of vulnerable instances and does not prove public access. Some deployments may sit behind a VPN or an identity-aware proxy. Others may expose a login page but enforce strong SAML and network policy. The count is useful for scoping a review, not for assigning a breach status.&lt;/p&gt;

&lt;p&gt;The deterministic search link is:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.zoomeye.ai/searchResult?q=YXBwPSJTb2xhcldpbmRzIE9yaW9uIg%3D%3D" rel="noopener noreferrer"&gt;https://www.zoomeye.ai/searchResult?q=YXBwPSJTb2xhcldpbmRzIE9yaW9uIg%3D%3D&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Re-run the query in the intended ZoomEye context and preserve the current time and scope. Treat the older observation as evidence of a prior index state only.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review the effective console
&lt;/h2&gt;

&lt;p&gt;Map every public DNS name and certificate to a console owner. Determine whether the service is directly exposed, behind a reverse proxy, or available only through a private network. Verify that the console's authentication method matches policy, including the treatment of local accounts when SAML or Windows authentication is enabled.&lt;/p&gt;

&lt;p&gt;Review account limitations for network segments and views. Confirm that an operator cannot change accounts, polling credentials, integrations, or advanced settings without an approved role. If the deployment uses a shared local administrator, replace it with named accounts and a controlled recovery process.&lt;/p&gt;

&lt;p&gt;Check the password and lockout policy for the account types that remain local. Test failed-login logging, session timeout, and the response to a disabled account. For SAML, verify the issuer, audience, certificate rotation, and group-to-role mapping. For Active Directory, confirm that only approved security groups map to privileged roles.&lt;/p&gt;

&lt;h2&gt;
  
  
  Operational limits
&lt;/h2&gt;

&lt;p&gt;The most important risks may sit behind the login page: stored SNMP and database credentials, polling accounts, integrations, and broad visibility into the monitored estate. Neither the ZoomEye count nor a successful login test reveals those relationships. The review should include an inventory of credential consumers and a plan to rotate any credential whose owner or scope cannot be established.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-secure-configuration.htm" rel="noopener noreferrer"&gt;SolarWinds, Secure configuration for the SolarWinds Platform&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-managing-web-accounts-sw1724.htm" rel="noopener noreferrer"&gt;SolarWinds, Manage web console user accounts&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-creating-new-accounts-sw1310.htm" rel="noopener noreferrer"&gt;SolarWinds, Create users in the SolarWinds Platform&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.zoomeye.ai/searchResult?q=YXBwPSJTb2xhcldpbmRzIE9yaW9uIg%3D%3D" rel="noopener noreferrer"&gt;ZoomEye count-only observation, &lt;code&gt;app="SolarWinds Orion"&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>zoomeye</category>
      <category>solarwinds</category>
      <category>identity</category>
    </item>
    <item>
      <title>Apache Amoro Management Counts Lead to Authentication and Lakehouse Control</title>
      <dc:creator>jeffrey</dc:creator>
      <pubDate>Thu, 19 Nov 2026 00:40:21 +0000</pubDate>
      <link>https://dev.to/jeffreyciend/apache-amoro-management-counts-lead-to-authentication-and-lakehouse-control-35d</link>
      <guid>https://dev.to/jeffreyciend/apache-amoro-management-counts-lead-to-authentication-and-lakehouse-control-35d</guid>
      <description>&lt;h1&gt;
  
  
  Apache Amoro Management Counts Lead to Authentication and Lakehouse Control
&lt;/h1&gt;

&lt;p&gt;Apache Amoro Management Service provides lakehouse management functions such as self-optimizing and data expiration. Those actions affect storage layout and data lifecycle, so the management UI and REST API are operational control planes rather than passive monitoring pages.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the measurement found
&lt;/h2&gt;

&lt;p&gt;A count-only ZoomEye SDK query on 2026-11-19 used &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and pagesize 1. &lt;code&gt;app="Amoro"&lt;/code&gt; returned zero. &lt;code&gt;title="Amoro"&lt;/code&gt; returned 11, and &lt;code&gt;http.body="Amoro"&lt;/code&gt; returned 260.&lt;/p&gt;

&lt;p&gt;The title count is small enough for ownership review. The body count may include project pages, downloads, and documentation. Neither result demonstrates that a management service is exposed or unauthenticated.&lt;/p&gt;

&lt;h2&gt;
  
  
  Identify the management service
&lt;/h2&gt;

&lt;p&gt;Amoro documentation describes an AMS HTTP server and dashboard. A local deployment example uses port 1630. The management service has REST authentication settings and dashboard login providers. The deployment guidance mentions token, basic, and JWT authentication types for the REST API and LDAP as a dashboard login provider.&lt;/p&gt;

&lt;p&gt;Collect the service URL, version, HTTP port, TLS termination, REST authentication type, dashboard login provider, and identity provider. Determine whether the UI and REST API use the same externally reachable hostname and whether one path bypasses the other.&lt;/p&gt;

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

&lt;p&gt;Identify which catalogs, tables, optimizer groups, and storage locations the service manages. Review who can trigger optimization or expiration and whether those actions are limited by tenant, project, or table policy. A read-only dashboard role should not be able to start lifecycle operations.&lt;/p&gt;

&lt;p&gt;Review credentials used to access the lakehouse and object storage. The AMS may coordinate with external systems through configured principals. Separate the user's dashboard identity from the service's backend credentials and confirm least privilege for both.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test authentication paths
&lt;/h2&gt;

&lt;p&gt;Test the dashboard login and the REST API independently. Verify that an unauthenticated request is denied, that an authenticated user without the required role is denied, and that the denial is consistent across create, update, and lifecycle endpoints. Do not run destructive optimization or expiration operations during discovery.&lt;/p&gt;

&lt;p&gt;Check proxy behavior. If a reverse proxy sets identity headers, verify that external clients cannot inject them. If JWT authentication is used, confirm issuer, audience, signature, and expiry handling against the product's supported configuration.&lt;/p&gt;

&lt;h2&gt;
  
  
  Validate before reporting
&lt;/h2&gt;

&lt;p&gt;Use title and body matches to generate a candidate list, then confirm each host with its owner and configuration record. A confirmed test environment might be intentionally open on a lab network. A production management service should have a documented boundary and a tested login path.&lt;/p&gt;

&lt;p&gt;The measured counts do not prove exposure. They identify a small set of pages worth checking. The useful conclusion is whether a confirmed Amoro management endpoint separates dashboard access from REST authority and whether its backend credentials are narrow enough for the lakehouse actions it performs.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://amoro.apache.org/" rel="noopener noreferrer"&gt;Apache Amoro&lt;/a&gt;, Apache Amoro project. Retrieved 2026-11-18.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://amoro.apache.org/docs/latest/configuration/ams-config/" rel="noopener noreferrer"&gt;AMS Configuration&lt;/a&gt;, Apache Amoro documentation. Retrieved 2026-11-18.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://amoro.apache.org/docs/latest/deployment/" rel="noopener noreferrer"&gt;Deployment&lt;/a&gt;, Apache Amoro documentation. Retrieved 2026-11-18.&lt;/li&gt;
&lt;li&gt;ZoomEye counts: &lt;code&gt;app="Amoro"&lt;/code&gt; 0; &lt;code&gt;title="Amoro"&lt;/code&gt; 11; &lt;code&gt;http.body="Amoro"&lt;/code&gt; 260. &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, pagesize 1, observed 2026-11-19 UTC+8.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>internetmeasurement</category>
      <category>zoomeye</category>
    </item>
    <item>
      <title>OpenAM Consoles and Session APIs Concentrate Administrative Authority</title>
      <dc:creator>jeffrey</dc:creator>
      <pubDate>Wed, 18 Nov 2026 21:22:10 +0000</pubDate>
      <link>https://dev.to/jeffreyciend/openam-consoles-and-session-apis-concentrate-administrative-authority-2210</link>
      <guid>https://dev.to/jeffreyciend/openam-consoles-and-session-apis-concentrate-administrative-authority-2210</guid>
      <description>&lt;h1&gt;
  
  
  OpenAM Consoles and Session APIs Concentrate Administrative Authority
&lt;/h1&gt;

&lt;p&gt;OpenAM provides an administrative console, REST authentication and session APIs, policy and identity services, and protocol endpoints for applications. These services belong to one identity platform but have different exposure rules. A public login endpoint can be necessary while the administrative console should remain on a management network or behind a strong access proxy.&lt;/p&gt;

&lt;p&gt;Open Identity Platform's documentation describes the administrative console at &lt;code&gt;/openam/console&lt;/code&gt; and the REST-like APIs under &lt;code&gt;/json/authenticate&lt;/code&gt; and &lt;code&gt;/json/sessions&lt;/code&gt;. The securing guide recommends a reverse proxy when exposing OAuth 2.0, OpenID Connect, or REST interfaces and discusses secure cookies and the optional return of &lt;code&gt;tokenId&lt;/code&gt; in a response body.&lt;/p&gt;

&lt;h2&gt;
  
  
  Measurement scope
&lt;/h2&gt;

&lt;p&gt;The ZoomEye observations were collected on 2026-11-18 at about 20:47 UTC with &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and pagesize 1.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Query&lt;/th&gt;
&lt;th&gt;Matches&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;title="OpenAM"&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;3,545&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;app="OpenAM"&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;210&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The counts show candidate assets but do not establish whether the console is reachable, whether &lt;code&gt;amadmin&lt;/code&gt; is enabled, or whether default credentials exist. The title may identify a login page, documentation, a customized console, or an unrelated proxy response. Verification belongs to the asset owner.&lt;/p&gt;

&lt;h2&gt;
  
  
  Map the public identity endpoints
&lt;/h2&gt;

&lt;p&gt;List every public OpenAM hostname and path. Separate browser login, protocol endpoints, REST sessions, and the administrative console. If the platform is behind a reverse proxy, confirm that the proxy preserves the correct host and path policy and does not expose an internal management route through a fallback rule.&lt;/p&gt;

&lt;p&gt;The REST authentication API should use HTTPS. Session tokens in a response body, URL, or log are credentials. If the platform returns &lt;code&gt;tokenId&lt;/code&gt; in the body for a non-browser integration, ensure the integration stores it securely and that the response is not cached by a shared proxy. Prefer cookie attributes and header handling that match the client type.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review administrative sessions
&lt;/h2&gt;

&lt;p&gt;Administrative access should require a named administrator and a strong authentication flow. Check whether default or shared administrative accounts are disabled. Review cookie scope, secure flags, session lifetime, and logout behavior. A session that remains valid after a password reset or account disable can preserve access longer than the response team expects.&lt;/p&gt;

&lt;p&gt;The console and REST APIs can share a realm and identity store while having different authorization checks. Test an ordinary identity against a console route, an administrative REST operation, and a protocol endpoint. The result should show which layer rejected the request and whether a proxy added another control.&lt;/p&gt;

&lt;h2&gt;
  
  
  Handle token exposure
&lt;/h2&gt;

&lt;p&gt;If a token may appear in a body, proxy logs, browser history, or support output, treat it as a potential credential exposure. Revoke the session and rotate any associated secret. Do not rely on deleting a log line. Correlate the token's creation time with access logs and with changes to administrators, policies, or identity providers.&lt;/p&gt;

&lt;p&gt;Review reverse proxy headers and trusted sources. An access rule based on client IP must account for the proxy address and must not accept a spoofed forwarding header from an untrusted client. An identity platform is a high-value target because compromise can affect every connected application.&lt;/p&gt;

&lt;p&gt;The recommended exposure model is deliberate: public protocol and login endpoints, a private or identity-aware administrative console, short-lived sessions, and a tested revocation path. ZoomEye counts help find candidates. The owner must show which candidate serves a console, a REST session API, or only a public login page.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://doc.openidentityplatform.org/openam/admin-guide/chap-admin-tools" rel="noopener noreferrer"&gt;OpenAM administration interfaces and tools&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://doc.openidentityplatform.org/openam/admin-guide/chap-securing" rel="noopener noreferrer"&gt;Securing OpenAM&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.zoomeye.ai/bi" rel="noopener noreferrer"&gt;ZoomEye&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>zoomeye</category>
      <category>identity</category>
      <category>sessionsecurity</category>
    </item>
    <item>
      <title>The Security Component in CVE-2026-112434: What the Public Record Says</title>
      <dc:creator>jeffrey</dc:creator>
      <pubDate>Wed, 18 Nov 2026 18:00:20 +0000</pubDate>
      <link>https://dev.to/jeffreyciend/the-security-component-in-cve-2026-112434-what-the-public-record-says-1pei</link>
      <guid>https://dev.to/jeffreyciend/the-security-component-in-cve-2026-112434-what-the-public-record-says-1pei</guid>
      <description>&lt;h1&gt;
  
  
  The Security Component in CVE-2026-112434: What the Public Record Says
&lt;/h1&gt;

&lt;p&gt;When a vendor says a logic issue was fixed with improved checks, the sentence is useful and incomplete. It identifies the failure class and tells defenders that a validation decision changed. It does not reveal the vulnerable function. CVE-2026-112434 needs to be handled with that distinction intact.&lt;/p&gt;

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

&lt;p&gt;Apple's advisory places CVE-2026-112434 in the Security component and says an app may gain root privileges. The CVE record assigns CVSS 3.1 7.8, CWE-693, local access, low complexity, low privileges, and no user interaction. Apple published the CVE on October 26, 2026. No reviewed source confirms active exploitation.&lt;/p&gt;

&lt;p&gt;The affected ranges are macOS Sequoia before 15.8.2, Tahoe before 26.7.2, and Golden Gate before 27.2. The component name is specific to macOS in the reviewed record.&lt;/p&gt;

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

&lt;p&gt;A logic issue means the code made an incorrect decision rather than necessarily mishandling memory. Apple says improved checks fixed it. In a Security component, that could involve an authorization state, a trust decision, or a privileged operation, but the advisory does not say which one.&lt;/p&gt;

&lt;p&gt;The known precondition is a local app on a vulnerable host. The app must reach the affected path. The CVSS vector assumes low privileges and no user interaction, but it does not prove that any app can trigger the bug. Local execution and the vulnerable build are both necessary.&lt;/p&gt;

&lt;p&gt;This is where evidence discipline matters. A defender can collect app signature, execution history, and privileged activity. A defender cannot honestly publish a signature that identifies the exploit without seeing supporting technical detail.&lt;/p&gt;

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

&lt;p&gt;The advertised impact is root privilege. That can broaden an attacker's access from the app context to protected system resources. Confidentiality, integrity, and availability are all scored high.&lt;/p&gt;

&lt;p&gt;The impact statement does not identify a persistence mechanism, a target file, or a remote service. Those details may emerge in later research, but they are not part of the reviewed public record.&lt;/p&gt;

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

&lt;p&gt;The three fixed macOS releases are Golden Gate 27.2, Tahoe 26.7.2, and Sequoia 15.8.2. Apple's references for this CVE point to those security pages. The reviewed record does not assign the local app issue to iOS, iPadOS, watchOS, tvOS, visionOS, or Safari.&lt;/p&gt;

&lt;p&gt;Asset teams should record which branch a Mac runs and whether the build is below the fixed threshold. The distinction between branch and build prevents a generic Apple update notice from being mistaken for proof of compliance.&lt;/p&gt;

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

&lt;p&gt;ZoomEye returned 3,429,599 observations for os="Mac OS X" and 0 for vul.cve="CVE-2026-112434" during the review. The first number describes broad OS fingerprints; the second describes the indexed CVE correlation. Neither is a statement that a particular Mac has the vulnerable Security logic.&lt;/p&gt;

&lt;p&gt;Publishing both numbers with their definitions is more useful than choosing the larger one and implying confirmed exposure.&lt;/p&gt;

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

&lt;p&gt;Install the fixed macOS release for the machine's branch and confirm the build after restart. Until that is complete, reduce the local execution surface by controlling unapproved apps and reviewing privileged helpers.&lt;/p&gt;

&lt;p&gt;A response plan should state what is known, what is inferred, and what remains unavailable. CVE-2026-112434 supports a clear patching decision. It does not support a claim that a particular app was exploited without host evidence.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://support.apple.com/en-us/149521" rel="noopener noreferrer"&gt;Apple security content for macOS Golden Gate 27.2&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://support.apple.com/en-us/149522" rel="noopener noreferrer"&gt;Apple security content for macOS Tahoe 26.7.2&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://support.apple.com/en-us/149523" rel="noopener noreferrer"&gt;Apple security content for macOS Sequoia 15.8.2&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://www.cve.org/CVERecord?id=CVE-2026-112434" rel="noopener noreferrer"&gt;CVE-2026-112434 CVE record&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2026-112434" rel="noopener noreferrer"&gt;NVD entry for CVE-2026-112434&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://www.cisecurity.org/advisory/multiple-vulnerabilities-in-apple-products-could-allow-for-arbitrary-code-execution_2026-121" rel="noopener noreferrer"&gt;CIS advisory on the October 2026 Apple updates&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>cybersecurity</category>
      <category>infosec</category>
      <category>security</category>
    </item>
  </channel>
</rss>
