<?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: OnaEiuspkz</title>
    <description>The latest articles on DEV Community by OnaEiuspkz (@onaeiuspkz).</description>
    <link>https://dev.to/onaeiuspkz</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%2F4127462%2F464d79fd-d761-42c0-8d3e-b8176e27b0c8.png</url>
      <title>DEV Community: OnaEiuspkz</title>
      <link>https://dev.to/onaeiuspkz</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/onaeiuspkz"/>
    <language>en</language>
    <item>
      <title>SOC response guide for CVE-2026-30612</title>
      <dc:creator>OnaEiuspkz</dc:creator>
      <pubDate>Mon, 16 Nov 2026 18:01:22 +0000</pubDate>
      <link>https://dev.to/onaeiuspkz/soc-response-guide-for-cve-2026-30612-1141</link>
      <guid>https://dev.to/onaeiuspkz/soc-response-guide-for-cve-2026-30612-1141</guid>
      <description>&lt;h1&gt;
  
  
  SOC response guide for CVE-2026-30612
&lt;/h1&gt;

&lt;p&gt;A security operations team investigating CVE-2026-30612 needs to answer three separate questions. Is the vulnerable Time4Popcorn updater installed? Did it run? Did it start unexpected content with high privilege?&lt;/p&gt;

&lt;p&gt;Those questions map to different telemetry and should not be collapsed into a single filename alert. The vulnerability involves an HTTP update channel that can execute code as SYSTEM or root. A service match establishes exposure. Process ancestry and network evidence are needed to assess activity.&lt;/p&gt;

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

&lt;p&gt;Eye Security's advisory identifies the affected Time4Popcorn fork and documents platform-specific updater paths. The CVE lists Windows at or below 6.2.1.18, macOS at or below 6.2.1.17, and Android at or below 3.5.0.173 as affected. It is CWE-494 with a CVSS 3.1 score of 9.8.&lt;/p&gt;

&lt;p&gt;The project is abandoned. Researchers registered available update domains, used the updater to disable the vulnerable component on Windows and macOS, and later transferred the domains to the Shadowserver Foundation. No vendor patch is available.&lt;/p&gt;

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

&lt;p&gt;The updater requests update instructions over HTTP. An attacker who can control a reachable domain or manipulate traffic can return a malicious response. Windows and macOS processes then launch the associated executable with high privilege and no user interaction. Android requires the user to accept an APK installation.&lt;/p&gt;

&lt;p&gt;From a detection perspective, the upstream network request and the child process are separate events. A proxy log can show contact with a documented domain without proving execution. Endpoint telemetry can show &lt;code&gt;Updater.exe&lt;/code&gt; or &lt;code&gt;PT.updd&lt;/code&gt; creating a process, but the examiner still needs to determine whether that child was expected. The project is abandoned, so an update-related child process merits scrutiny.&lt;/p&gt;

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

&lt;p&gt;Unexpected SYSTEM or root execution can support persistence, credential access, defense evasion, and lateral movement. Responders should treat it as a privileged-code-execution lead and preserve volatile evidence before remediation when feasible.&lt;/p&gt;

&lt;p&gt;Eye Security's scale research found millions of estimated clients and connections from many network types. The figures help prioritize the software search. They do not attribute an event to a particular organization or prove malicious exploitation on a specific host.&lt;/p&gt;

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

&lt;p&gt;The Windows search should include the "Update service", &lt;code&gt;Updater.exe&lt;/code&gt;, and both standard Program Files paths. The macOS search should include &lt;code&gt;PT.updd&lt;/code&gt;, &lt;code&gt;/Library/LaunchDaemons/PT.updd.plist&lt;/code&gt;, and package receipts where available. Android review should use package identity, version, and installation history.&lt;/p&gt;

&lt;p&gt;Teams should correlate service or daemon creation with endpoint EDR data, DNS and proxy history, and software inventory. Querying all historical traffic for the documented domains can identify systems that communicated before the updater was disabled, but a domain match alone does not establish a response payload.&lt;/p&gt;

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

&lt;p&gt;The selected public measurement is 102 from ZoomEye &lt;code&gt;title="Popcorn Time"&lt;/code&gt;. The application-fingerprint query returned 11, and the exact CVE filter returned 0.&lt;/p&gt;

&lt;p&gt;Exposure 102 describes title-matching assets and does not identify vulnerable hosts. Public measurements can support an external picture, while SOC decisions require internal evidence. This distinction should be preserved in incident notes and executive updates.&lt;/p&gt;

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

&lt;p&gt;The first immediate step is to isolate the endpoint from untrusted network paths if unexpected privileged execution is present. Preserve process trees, command lines, file hashes, service or daemon settings, and relevant network records. Then apply the documented updater disablement or proceed directly to removal under incident procedures.&lt;/p&gt;

&lt;p&gt;The routine clean-up uses &lt;code&gt;sc.exe stop "Update service"&lt;/code&gt; and a disabled service start type on Windows, or &lt;code&gt;launchctl unload -w /Library/LaunchDaemons/PT.updd.plist&lt;/code&gt; on macOS. Verification should occur after reboot. Full uninstall follows because the rest of the application remains unsupported and unsafe.&lt;/p&gt;

&lt;p&gt;Detection content should combine process ancestry with path validation and network context. It should also label the alert as potential exploit activity rather than confirmed compromise until the child executable and surrounding events are reviewed. That structure gives analysts a defensible path from inventory to incident.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://labs.eye.security/cve-2026-30612-a-vulnerability-in-time4popcorn-popcorntime/" rel="noopener noreferrer"&gt;Eye Security CVE-2026-30612 advisory&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://labs.eye.security/operation-ixim-preventing-a-botnet-of-millions-of-popcorn-time-users/" rel="noopener noreferrer"&gt;Eye Security Operation IXIM incident details&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2026-30612" rel="noopener noreferrer"&gt;NVD CVE-2026-30612&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.securityweek.com/dead-popcorn-time-updater-put-millions-of-computers-at-risk-of-takeover/" rel="noopener noreferrer"&gt;SecurityWeek report&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>vulnerability</category>
      <category>cve202630612</category>
    </item>
    <item>
      <title>PartKeepr inventory authority must be checked across forks and APIs</title>
      <dc:creator>OnaEiuspkz</dc:creator>
      <pubDate>Mon, 16 Nov 2026 14:43:06 +0000</pubDate>
      <link>https://dev.to/onaeiuspkz/partkeepr-inventory-authority-must-be-checked-across-forks-and-apis-d5l</link>
      <guid>https://dev.to/onaeiuspkz/partkeepr-inventory-authority-must-be-checked-across-forks-and-apis-d5l</guid>
      <description>&lt;h1&gt;
  
  
  PartKeepr inventory authority must be checked across forks and APIs
&lt;/h1&gt;

&lt;p&gt;PartKeepr is an inventory manager for electronic components. It records part numbers, stock, locations, suppliers, attachments, and the people who may change them. That makes it more sensitive than a simple catalogue, especially when the inventory supports purchasing or production.&lt;/p&gt;

&lt;p&gt;The 2026-11-15 count-only observations used page 1, pagesize 1, and &lt;code&gt;sub_type=all&lt;/code&gt;. &lt;code&gt;app="PartKeepr"&lt;/code&gt; returned 0, &lt;code&gt;title="PartKeepr"&lt;/code&gt; returned 591, and &lt;code&gt;http.body="PartKeepr"&lt;/code&gt; returned 925. The title and body counts identify possible product references; the zero application count is not an absence claim.&lt;/p&gt;

&lt;h2&gt;
  
  
  Treat the fork as part of the product identity
&lt;/h2&gt;

&lt;p&gt;The original PartKeepr repository is archived, and a maintained fork documents a role-based permission system. A deployment may run either lineage or a local modification. The software name alone does not establish the authorization behavior.&lt;/p&gt;

&lt;p&gt;Record the repository and version, then review the account model actually in use. Confirm who can create and remove users, change stock, edit part records, and access uploads. Separate normal inventory work from administration and from API access.&lt;/p&gt;

&lt;h2&gt;
  
  
  Inventory API clients
&lt;/h2&gt;

&lt;p&gt;Inventory clients may read or update records without a browser session. Record each client's owner, credential type, allowed operations, and retirement date. Test whether a user-scoped credential inherits the expected roles and whether disabled users lose access promptly.&lt;/p&gt;

&lt;p&gt;Protect the API and web interface with HTTPS and a management boundary. If a reverse proxy supplies identity, confirm that it strips untrusted headers. Protect backups because they can contain the whole inventory and its attachments.&lt;/p&gt;

&lt;h2&gt;
  
  
  Validate a discovery candidate
&lt;/h2&gt;

&lt;p&gt;Open the candidate page and confirm the PartKeepr login or a product-specific asset before assigning it to an owner. Check the title, login form, static paths, and certificate together. A title match can be documentation, a demo, or an old page.&lt;/p&gt;

&lt;p&gt;For confirmed systems, test read, stock update, user administration, and API access with two roles. Confirm that a normal user cannot change another team's records or create a new administrator. Preserve the effective rule and the audit record.&lt;/p&gt;

&lt;p&gt;PartKeepr is old enough that fork and version drift are part of the security review. The inventory should name the codebase, the permission model, and the API clients before it calls the asset known.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/partkeepr/PartKeepr" rel="noopener noreferrer"&gt;PartKeepr archived repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ashcoft/PartKeepr" rel="noopener noreferrer"&gt;Maintained PartKeepr fork&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/partkeepr/PartKeepr/blob/master/documentation/Installation.md" rel="noopener noreferrer"&gt;PartKeepr installation documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>autonomous</category>
    </item>
    <item>
      <title>Macaroon caveats attenuate authority, but discharges still need a trust policy</title>
      <dc:creator>OnaEiuspkz</dc:creator>
      <pubDate>Mon, 16 Nov 2026 11:22:08 +0000</pubDate>
      <link>https://dev.to/onaeiuspkz/macaroon-caveats-attenuate-authority-but-discharges-still-need-a-trust-policy-1khj</link>
      <guid>https://dev.to/onaeiuspkz/macaroon-caveats-attenuate-authority-but-discharges-still-need-a-trust-policy-1khj</guid>
      <description>&lt;h1&gt;
  
  
  Macaroon caveats attenuate authority, but discharges still need a trust policy
&lt;/h1&gt;

&lt;p&gt;A macaroon packages a root identifier, a chain of caveats, and a signature. Its useful property is controlled delegation. A holder can append caveats that restrict where, when, or how the credential may be used, producing a narrower credential without asking the issuer for a new token. The verifier evaluates the caveats and the signature chain before allowing the request.&lt;/p&gt;

&lt;p&gt;The original Macaroons paper describes first-party caveats that the resource server can check locally and third-party caveats that require a discharge macaroon from another service. That flexibility makes macaroons useful for distributed authorization and constrained delegation. It also means the verifier must understand the caveat language and the parties allowed to discharge each restriction.&lt;/p&gt;

&lt;h2&gt;
  
  
  Attenuation only works when the chain is intact
&lt;/h2&gt;

&lt;p&gt;A macaroon signature is derived through a cryptographic chain over the token contents. Appending a caveat changes the chain, and the verifier must recompute it with the root key. If an application accepts a caveat list without verifying the chain, an attacker can add permissive-looking text or claim authority the issuer never granted.&lt;/p&gt;

&lt;p&gt;The root secret remains the trust anchor. A verifier that shares one root key across unrelated services can accept a macaroon minted for another purpose unless the caveats and service context separate them. Use distinct roots or explicit audience caveats, and rotate roots with a planned transition path.&lt;/p&gt;

&lt;h2&gt;
  
  
  Third-party caveats need discharge validation
&lt;/h2&gt;

&lt;p&gt;A third-party caveat names a location and a discharge condition. The verifier obtains a discharge macaroon and checks that it is bound to the original token, that its signature is valid, and that its own caveats are satisfied. Accepting any discharge token with the right label is not enough. The discharge service must also be authorized to speak for that caveat.&lt;/p&gt;

&lt;p&gt;This creates a dependency graph. A request may contact several discharge services, and a failure in one should not silently convert into approval. Define which failures are terminal, whether results can be cached, and how stale discharge evidence is handled. The authorization log should record the caveat identifiers and discharge decisions without copying secrets or full credentials.&lt;/p&gt;

&lt;h2&gt;
  
  
  Revocation is a separate control
&lt;/h2&gt;

&lt;p&gt;Macaroons are bearer credentials. Attenuation reduces what a holder can do, but it does not provide an automatic revocation list or a central check on every use. A service that needs immediate revocation must add a database, a short lifetime, a token-version check, or another trusted state source. The design should state which mechanism applies when a user is disabled, a device is lost, or a root key is compromised.&lt;/p&gt;

&lt;p&gt;Storage and transport also matter. A macaroon may be placed in a cookie or authorization header, so browser policies, TLS, and application logs affect exposure. Do not log the full credential. If a macaroon is copied from a support bundle, treat it as a live secret until expiration or revocation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review the caveat semantics
&lt;/h2&gt;

&lt;p&gt;The verifier should reject unknown caveats that it cannot evaluate, enforce a maximum caveat count, and avoid substring matches that confuse &lt;code&gt;user=alice&lt;/code&gt; with &lt;code&gt;user=alice-admin&lt;/code&gt;. Caveat values should be parsed with a defined grammar and compared against trusted request context. A free-form caveat that an application merely prints into a log is not an authorization control.&lt;/p&gt;

&lt;p&gt;Macaroons are valuable when delegation needs to be narrow and offline attenuation improves the workflow. They are weaker when the organization cannot describe the trust root, discharge services, and revocation path. The operational question is whether every party that can mint, attenuate, discharge, or verify a macaroon has a clear role in the authorization chain.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://research.google/pubs/macaroons-cookies-with-contextual-caveats-for-decentralized-authorization-in-the-cloud/" rel="noopener noreferrer"&gt;Macaroons: Cookies with Contextual Caveats for Decentralized Authorization in the Cloud&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/lightninglabs/L402/blob/master/macaroon-spec.md" rel="noopener noreferrer"&gt;Macaroon specification implementation notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/macaroon-rs/macaroon/blob/main/README.md" rel="noopener noreferrer"&gt;Macaroon library overview&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>authorization</category>
      <category>distributedsystems</category>
    </item>
    <item>
      <title>CMC enrollment must authorize each certificate action, not just the connection</title>
      <dc:creator>OnaEiuspkz</dc:creator>
      <pubDate>Mon, 16 Nov 2026 07:21:48 +0000</pubDate>
      <link>https://dev.to/onaeiuspkz/cmc-enrollment-must-authorize-each-certificate-action-not-just-the-connection-56ld</link>
      <guid>https://dev.to/onaeiuspkz/cmc-enrollment-must-authorize-each-certificate-action-not-just-the-connection-56ld</guid>
      <description>&lt;h1&gt;
  
  
  CMC enrollment must authorize each certificate action, not just the connection
&lt;/h1&gt;

&lt;p&gt;Certificate Management over CMS (CMC) carries certificate requests, responses, revocation, and status information inside CMS messages. The July 2026 revision in RFC 10002 modernizes the message structures, while RFC 10003 covers transport and RFC 10004 lists compliance requirements. A registration authority or certificate authority that only authenticates the HTTPS connection is missing much of CMC's security model.&lt;/p&gt;

&lt;p&gt;CMC messages can be signed with CMS &lt;code&gt;SignedData&lt;/code&gt;, authenticated with &lt;code&gt;AuthenticatedData&lt;/code&gt;, or encrypted with &lt;code&gt;EnvelopedData&lt;/code&gt;. A Full PKI Request can contain several controls, including identity proof, proof of possession, transaction identifiers, nonces, modification requests, and certificate acceptance. The receiver must verify the CMS signature before acting on those controls. RFC 10002 also requires a Full PKI Response when a request fails, remains pending, or needs to return information beyond the issued certificates.&lt;/p&gt;

&lt;p&gt;That message model creates a useful audit boundary. The connection authenticates the transport peer. The CMS control authenticates the requested action at the PKI layer. A registrar should record which control caused an issuance, which transaction it belongs to, and whether the end entity accepted the result. This matters when an enrollment request crosses an RA, a CA, and one or more back-end signing services.&lt;/p&gt;

&lt;h2&gt;
  
  
  Bind the request to a transaction
&lt;/h2&gt;

&lt;p&gt;RFC 10004 requires transaction IDs, sender nonces, and recipient nonces across end entities, RAs, and CAs. Their presence is not enough if the service does not preserve them. A CA should reject a response that does not match the outstanding request, and a client should reject a response that reuses a nonce or references an unknown transaction. If the RA stores only a certificate serial number, investigators lose the link between the approval and the request that produced it.&lt;/p&gt;

&lt;p&gt;Proof-of-possession controls need the same treatment. A signed request can show that a key signed the request, while a POP link random value binds the key proof to the transaction. The server should treat a missing or stale POP witness as a failed enrollment, not as an optional hint. Batch requests add more state, so each response body and &lt;code&gt;bodyPartID&lt;/code&gt; must map back to the correct request entry.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate approval from issuance
&lt;/h2&gt;

&lt;p&gt;The end entity can ask for changes. The RA can modify a request or add extensions. The CA decides whether to issue the certificate. Keeping these decisions as separate records prevents a common failure where an account with permission to submit a request is also treated as an authority to approve it.&lt;/p&gt;

&lt;p&gt;Certificate acceptance is another explicit action. When the CA asks for confirmation, the client sends a Full PKI Request containing the acceptance control, and the CA returns a confirming Full PKI Response. Automation should wait for that response before placing the certificate into service. Otherwise a rollback or a rejected certificate may still be deployed by a job that only saw the issuance response.&lt;/p&gt;

&lt;h2&gt;
  
  
  Operational checks
&lt;/h2&gt;

&lt;p&gt;Inventory every CMC endpoint, including HTTP, email, and any other supported transport. Restrict algorithm policy at the CMS layer and reject unsigned controls when policy requires signatures. Keep request and response bodies long enough for incident review, but redact private-key archival material and other sensitive payloads. Alert on repeated &lt;code&gt;badMessageCheck&lt;/code&gt; failures, unknown transaction IDs, nonce reuse, and a spike in pending confirmations.&lt;/p&gt;

&lt;p&gt;Finally, test interoperability against the published CMC test cases and each vendor's supported control set. RFC 10004 describes requirements by role, and a product that calls itself CMC-compatible can still omit controls that another implementation depends on. Record the supported controls in the PKI service inventory so a later upgrade does not silently remove identity proof, POP, or acceptance handling.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc10002.html" rel="noopener noreferrer"&gt;RFC 10002: Certificate Management over CMS (CMC)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc10003.html" rel="noopener noreferrer"&gt;RFC 10003: CMC Transport Protocols&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc10004.html" rel="noopener noreferrer"&gt;RFC 10004: CMC Compliance Requirements&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>pki</category>
      <category>certificatemanagement</category>
    </item>
    <item>
      <title>Ghostfolio inventory starts with access, portfolio visibility, and proxy trust</title>
      <dc:creator>OnaEiuspkz</dc:creator>
      <pubDate>Mon, 16 Nov 2026 04:04:22 +0000</pubDate>
      <link>https://dev.to/onaeiuspkz/ghostfolio-inventory-starts-with-access-portfolio-visibility-and-proxy-trust-4f1b</link>
      <guid>https://dev.to/onaeiuspkz/ghostfolio-inventory-starts-with-access-portfolio-visibility-and-proxy-trust-4f1b</guid>
      <description>&lt;h1&gt;
  
  
  Ghostfolio inventory starts with access, portfolio visibility, and proxy trust
&lt;/h1&gt;

&lt;p&gt;Ghostfolio is a self-hosted wealth-management application. Its public value is a consolidated view of accounts, positions, and performance. The security question is who can see that view, which authentication path produced the session, and whether the application is interpreting proxy headers from a trusted source.&lt;/p&gt;

&lt;p&gt;A count-only ZoomEye observation on 2026-11-16 found 0 matches for &lt;code&gt;app="Ghostfolio"&lt;/code&gt;, 110 for &lt;code&gt;title="Ghostfolio"&lt;/code&gt;, and 11,205 for &lt;code&gt;http.body="Ghostfolio"&lt;/code&gt;. The queries used &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and pagesize 1. The body result includes documentation, repositories, mentions, and unrelated pages, so it is not an instance count. The title result is a narrower inventory signal, while the zero application fingerprint means product discovery must use page and response validation.&lt;/p&gt;

&lt;p&gt;The official README documents three access paths that matter during review: local email and password authentication, optional security-token access, and an experimental OpenID Connect mode. It also exposes &lt;code&gt;TRUST_PROXY&lt;/code&gt; and an optional security-headers feature. Those are separate controls. Enabling OIDC does not remove local accounts unless the deployment does so. A security token is a credential for an API path and needs the same ownership and revocation review as a user account.&lt;/p&gt;

&lt;h2&gt;
  
  
  Validate the proxy boundary
&lt;/h2&gt;

&lt;p&gt;Ghostfolio can run behind a reverse proxy. The &lt;code&gt;TRUST_PROXY&lt;/code&gt; setting tells the application which proxy hops may supply client-address information. Set it to the actual path, not an unrestricted value. A misconfigured trust boundary can let a direct client influence rate limiting, audit logs, or redirect decisions. Verify the application is reachable only through the intended proxy and that the proxy removes untrusted forwarding headers.&lt;/p&gt;

&lt;p&gt;The README makes HTTP security headers optional. A public deployment should enable the feature or apply equivalent headers at the edge, then inspect the response through the same hostname users visit. Test content security policy, frame restrictions, referrer policy, and transport security after login and on API responses. A header present on the marketing page and absent from the authenticated application does not protect the portfolio view.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review identity and data scope
&lt;/h2&gt;

&lt;p&gt;Inventory every enabled user, security token, OIDC issuer, callback URL, and trusted proxy. For OIDC, check issuer discovery, client secret storage, callback registration, and the scope requested. For local authentication, check account creation, password reset, session lifetime, and administrator recovery. For tokens, record purpose, owner, creation time, and last use.&lt;/p&gt;

&lt;p&gt;The application holds financial data and may receive external market data. Separate read access to a dashboard from the ability to change accounts, import transactions, or manage users. If the deployment uses multiple users, verify that portfolio and account boundaries are enforced by the application, not only by separate browser tabs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Turn a title hit into evidence
&lt;/h2&gt;

&lt;p&gt;A title match should lead to a safe GET of the root page, followed by an authenticated check performed by the owner. Record the final URL, response title, headers, application assets, version evidence, authentication mode, and whether registration is open. Do not submit credentials or attempt access to another organization's instance.&lt;/p&gt;

&lt;p&gt;The 110-title observation is useful for finding candidates. It cannot show which candidates are live Ghostfolio deployments, which are protected, or which contain sensitive financial records. Inventory quality depends on confirming the product marker, the auth configuration, and the owner. Those checks also produce the evidence needed to fix the boundary when the service was exposed by mistake.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/ghostfolio/ghostfolio/blob/main/README.md" rel="noopener noreferrer"&gt;Ghostfolio self-hosting README&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ghostfolio/ghostfolio/blob/main/SECURITY.md" rel="noopener noreferrer"&gt;Ghostfolio security policy&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.zoomeye.ai/searchResult?q=dGl0bGU9Ikdob3N0Zm9saW8i" rel="noopener noreferrer"&gt;ZoomEye count-only observation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>zoomeye</category>
      <category>wealthmanagement</category>
      <category>assetinventory</category>
    </item>
    <item>
      <title>Knot Resolver's web zero is not a DNS inventory zero</title>
      <dc:creator>OnaEiuspkz</dc:creator>
      <pubDate>Mon, 16 Nov 2026 00:40:26 +0000</pubDate>
      <link>https://dev.to/onaeiuspkz/knot-resolvers-web-zero-is-not-a-dns-inventory-zero-47ok</link>
      <guid>https://dev.to/onaeiuspkz/knot-resolvers-web-zero-is-not-a-dns-inventory-zero-47ok</guid>
      <description>&lt;h1&gt;
  
  
  Knot Resolver's web zero is not a DNS inventory zero
&lt;/h1&gt;

&lt;p&gt;Knot Resolver is a caching and validating DNS resolver. Its primary service is the DNS protocol, not an HTML application. A measurement that depends on an application fingerprint, a page title, or an HTTP body can therefore produce a very small result even when resolvers are operating.&lt;/p&gt;

&lt;p&gt;The 2026-11-16 count-only observation used &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and pagesize 1. &lt;code&gt;app="Knot Resolver"&lt;/code&gt; returned 0, &lt;code&gt;title="Knot Resolver"&lt;/code&gt; returned 0, and &lt;code&gt;http.body="Knot Resolver"&lt;/code&gt; returned 166. The 166 pages are likely to include documentation and management material, but the count alone cannot tell us which are resolver services.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Query role&lt;/th&gt;
&lt;th&gt;Exact dork&lt;/th&gt;
&lt;th&gt;Observed total&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Application fingerprint&lt;/td&gt;
&lt;td&gt;&lt;code&gt;app="Knot Resolver"&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Page title&lt;/td&gt;
&lt;td&gt;&lt;code&gt;title="Knot Resolver"&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HTTP body&lt;/td&gt;
&lt;td&gt;&lt;code&gt;http.body="Knot Resolver"&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;166&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  DNS has its own discovery surface
&lt;/h2&gt;

&lt;p&gt;Knot Resolver documentation covers recursive service behavior, DNS-over-TLS, DNS-over-HTTPS, and optional web management. A resolver may listen on port 53, 853, or an HTTPS endpoint under a deployment-specific path. The software name may never appear in the HTTP title.&lt;/p&gt;

&lt;p&gt;An organization should start from its DNS architecture and owned network records: recursive resolvers, forwarders, authoritative servers, resolver caches, and administrative interfaces. Then it can verify which process serves each address. A generic internet search can support that work, but it cannot replace network ownership data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Do not convert documentation hits into resolvers
&lt;/h2&gt;

&lt;p&gt;The body result can include tutorials, service documentation, and product pages. A host in the result should be classified as a candidate until an authorized check confirms the expected DNS behavior. Even a DNS response does not prove the software family unless the fingerprint and configuration are reviewed.&lt;/p&gt;

&lt;p&gt;The zero title and application counts are still useful as negative evidence for those exact fields. They show that the selected product-name labels were not represented in this index observation. They do not establish that no Knot Resolver deployment is reachable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review resolver policy
&lt;/h2&gt;

&lt;p&gt;For owned resolvers, the meaningful controls include recursion exposure, query policy, response-rate behavior, DNSSEC validation, encrypted transport, cache poisoning defenses, and web-management access. A resolver that serves a private client population should not accept arbitrary public recursion.&lt;/p&gt;

&lt;p&gt;Logging should capture queries only to the extent required by policy and law. DNS data can reveal user activity, so broad query logging can create a privacy problem even when it helps incident response. Restrict access to resolver administration and test whether policy changes are audited.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use a protocol-aware follow-up
&lt;/h2&gt;

&lt;p&gt;The selected link below is the 166-result body query. It is a weak signal and should be treated as a discovery aid. The next step for an owned environment is to correlate DNS listeners and certificates with the resolver process, then verify configuration ownership.&lt;/p&gt;

&lt;p&gt;The conclusion is not that Knot Resolver is invisible. It is that DNS services require a measurement plan built around protocols and infrastructure records. A web page count can add context, but it cannot replace a resolver inventory.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://knot-resolver.readthedocs.io/en/stable/" rel="noopener noreferrer"&gt;Knot Resolver documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://knot-resolver.readthedocs.io/en/stable/daemon-bindings-net_server.html" rel="noopener noreferrer"&gt;Knot Resolver network services and bindings&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://knot-resolver.readthedocs.io/en/stable/config-network.html" rel="noopener noreferrer"&gt;Knot Resolver networking configuration&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.zoomeye.ai/searchResult?q=aHR0cC5ib2R5PSJLbm90IFJlc29sdmVyIg%3D%3D" rel="noopener noreferrer"&gt;ZoomEye count-only observation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>zoomeye</category>
      <category>dns</category>
      <category>visibility</category>
    </item>
    <item>
      <title>OpenBoxes: Location-Scoped Inventory Permissions Need Concrete Tests</title>
      <dc:creator>OnaEiuspkz</dc:creator>
      <pubDate>Sun, 15 Nov 2026 21:21:49 +0000</pubDate>
      <link>https://dev.to/onaeiuspkz/openboxes-location-scoped-inventory-permissions-need-concrete-tests-1204</link>
      <guid>https://dev.to/onaeiuspkz/openboxes-location-scoped-inventory-permissions-need-concrete-tests-1204</guid>
      <description>&lt;h1&gt;
  
  
  OpenBoxes: Location-Scoped Inventory Permissions Need Concrete Tests
&lt;/h1&gt;

&lt;p&gt;Inventory systems reveal stock levels, supplier relationships, shipment status, and the locations that hold sensitive supplies. OpenBoxes uses permission levels that can apply across the system or at a specific location. A small internet count does not make that model less important. It creates an opportunity to review each candidate precisely.&lt;/p&gt;

&lt;p&gt;OpenBoxes' permission guide says every user has a level that controls what they can see and do, with system-wide and location-specific settings. The user guide describes location roles and a default location. The onboarding documentation recommends changing the default administrator password and role and creating users with the appropriate authority. The product documentation also describes locations that manage inventory and non-depot locations that may only submit or view requests.&lt;/p&gt;

&lt;p&gt;These distinctions make location the central authorization context. A user with stock access at one depot should not be able to view or transact at another depot unless the policy grants it. A user who can submit a request from a ward should not be able to approve stock movement at a depot.&lt;/p&gt;

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

&lt;p&gt;A count-only ZoomEye AI probe on 2026-11-16 used &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and page size 1. &lt;code&gt;title="OpenBoxes"&lt;/code&gt; returned 4 matches. &lt;code&gt;app="OpenBoxes"&lt;/code&gt; returned 0, and &lt;code&gt;http.body="OpenBoxes"&lt;/code&gt; returned 197. The body count can include documentation and project pages. Four title matches are a narrow observation and may include demos or references rather than production systems.&lt;/p&gt;

&lt;p&gt;The count is not proof of a public inventory system. It is a small candidate set that should be verified by owner and hostname.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the location boundary
&lt;/h2&gt;

&lt;p&gt;Create a user with a role at location A and no role at location B. Test inventory view, stock movement, shipment receipt, and request submission at both locations. Then test a user whose default role is no access but whose location role grants one workflow. The result should match the location-specific grant, not fall back to a broad default.&lt;/p&gt;

&lt;p&gt;Test the location hierarchy. A regional manager may need access to a group of locations, while a single depot user should not inherit the regional scope. Review how the application resolves the hierarchy in the UI and in any API or import path.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review imports and shipments
&lt;/h2&gt;

&lt;p&gt;Bulk imports, shipment rollback, and data imports are administrative operations. A user who can create a stock count should not automatically be able to roll back a shipment or import new products. Separate these actions into narrow roles and record the file, actor, target location, and result.&lt;/p&gt;

&lt;p&gt;Shipments can traverse several locations. Verify that each transition checks the actor's authority at both the source and destination. A receiving user should not be able to alter a shipment after it has been finalized unless the policy grants a correction workflow with an audit record.&lt;/p&gt;

&lt;h2&gt;
  
  
  Protect administrator access
&lt;/h2&gt;

&lt;p&gt;Use a named administrator account and a unique strong credential. Change the default administrator password and role as part of onboarding. Restrict internet access to the administrative path where possible and put the application behind a trusted identity proxy if that integration is supported.&lt;/p&gt;

&lt;p&gt;Log role assignment, location-role changes, stock adjustments, imports, and shipment rollback. Review the logs for users who have broad default roles they no longer need.&lt;/p&gt;

&lt;p&gt;OpenBoxes illustrates a general inventory problem: the most important authorization decision is often not "can this user log in?" It is "at which location and for which transaction?" The four title matches should be treated as candidates for that exact test. ZoomEye can narrow the public edge; the location-role matrix determines whether the edge is safe.&lt;/p&gt;

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

&lt;ol&gt;
&lt;li&gt;OpenBoxes, "Intro to User Permissions." &lt;a href="https://help.openboxes.com/article/64-intro-to-user-permissions" rel="noopener noreferrer"&gt;https://help.openboxes.com/article/64-intro-to-user-permissions&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;OpenBoxes, "Create and Manage users." &lt;a href="https://help.openboxes.com/article/89-manage-users" rel="noopener noreferrer"&gt;https://help.openboxes.com/article/89-manage-users&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;OpenBoxes, "Onboarding." &lt;a href="https://docs.openboxes.com/en/develop/user-guide/onboarding/" rel="noopener noreferrer"&gt;https://docs.openboxes.com/en/develop/user-guide/onboarding/&lt;/a&gt;
&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>security</category>
      <category>zoomeye</category>
      <category>assetinventory</category>
      <category>openboxes</category>
    </item>
    <item>
      <title>Threat-modeling wiki confidentiality after GROWI CVE-2026-105272</title>
      <dc:creator>OnaEiuspkz</dc:creator>
      <pubDate>Sun, 15 Nov 2026 18:02:53 +0000</pubDate>
      <link>https://dev.to/onaeiuspkz/threat-modeling-wiki-confidentiality-after-growi-cve-2026-105272-51bl</link>
      <guid>https://dev.to/onaeiuspkz/threat-modeling-wiki-confidentiality-after-growi-cve-2026-105272-51bl</guid>
      <description>&lt;h1&gt;
  
  
  Threat-modeling wiki confidentiality after GROWI CVE-2026-105272
&lt;/h1&gt;

&lt;h2&gt;
  
  
  Overview
&lt;/h2&gt;

&lt;p&gt;A wiki permission model often assumes that each revision inherits the page's access boundary. CVE-2026-105272 broke that assumption in GROWI. A page could authorize a request while its revision came from another page. The result was an authenticated read bypass for bodies and comments.&lt;/p&gt;

&lt;p&gt;JVN records CWE-639, CVSS 4.0 2.3, and CVSS 3.0 4.2. The affected versions are v3.2.10 through v8.0.6, and the fix is v8.0.7.&lt;/p&gt;

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

&lt;p&gt;Several handlers received &lt;code&gt;pageId&lt;/code&gt; and &lt;code&gt;revisionId&lt;/code&gt;. The access check covered the page. It did not prove that the revision belonged to the page. A logged-in user could combine a viewable page ID with a foreign revision ID. The response could reveal the foreign body. The comment route had the same flaw and could return comments and creator details.&lt;/p&gt;

&lt;p&gt;The user needed a valid account and knowledge of the target revision ID. GROWI's MongoDB ObjectIds include time, per-process randomness, and a counter. They are not secret tokens. A user can create revisions and observe the pattern. Edit permission was not required.&lt;/p&gt;

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

&lt;p&gt;This is a confidentiality threat across page boundaries. The affected assets are restricted bodies, discussions, and related metadata. The actors are authenticated users who might otherwise have limited page access. The precondition is access to a revision identifier and a viewable page from which to submit the mixed request.&lt;/p&gt;

&lt;p&gt;The maintainer states that the read creates no revision and leaves no trace in that workflow. The review did not identify an in-the-wild exploitation report. The flaw alone does not provide server execution.&lt;/p&gt;

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

&lt;p&gt;GROWI v3.2.10 through v8.0.6 is affected. The page-body path has existed since v3.3.0, and the comment endpoint accepted a revision ID from at least v3.2.10. Share-link access was not affected.&lt;/p&gt;

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

&lt;p&gt;ZoomEye returned 401 product-title matches for GROWI on 2026-11-15. The exact CVE Filter returned zero. Product title exposure identifies candidates, not vulnerable systems. A threat model should assign confidence separately for product presence, version, account reachability, and evidence of a request.&lt;/p&gt;

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

&lt;p&gt;GROWI v8.0.7 verifies that a client-supplied revision belongs to the page. If it does not, reads fall back to the page's own latest revision or comments. Comment write operations reject a foreign revision. The advisory contains no workaround.&lt;/p&gt;

&lt;p&gt;Upgrade to v8.0.7 or later. Then assess whether page permissions match the confidentiality level of stored content, whether all accounts still need access, and whether application logs can answer the questions the advisory leaves unresolved. Do not infer safety from the CVSS score alone.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://jvn.jp/en/jp/JVN51223238/" rel="noopener noreferrer"&gt;JVN#51223238&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/growilabs/growi/security/advisories/GHSA-m72c-xgjf-56ww" rel="noopener noreferrer"&gt;GROWI advisory GHSA-m72c-xgjf-56ww&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/growilabs/growi/releases/tag/v8.0.7" rel="noopener noreferrer"&gt;GROWI v8.0.7 release&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://osv.dev/vulnerability/CVE-2026-105272" rel="noopener noreferrer"&gt;OSV CVE-2026-105272&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>growi</category>
      <category>threatmodeling</category>
    </item>
    <item>
      <title>Patch Verification Checklist for CVE-2026-65339 Across Apple Platforms</title>
      <dc:creator>OnaEiuspkz</dc:creator>
      <pubDate>Sun, 15 Nov 2026 14:42:21 +0000</pubDate>
      <link>https://dev.to/onaeiuspkz/patch-verification-checklist-for-cve-2026-65339-across-apple-platforms-2e2l</link>
      <guid>https://dev.to/onaeiuspkz/patch-verification-checklist-for-cve-2026-65339-across-apple-platforms-2e2l</guid>
      <description>&lt;h1&gt;
  
  
  Patch Verification Checklist for CVE-2026-65339 Across Apple Platforms
&lt;/h1&gt;

&lt;p&gt;A remediation ticket for CVE-2026-65339 should not close because an update was offered. It should close when each device runs an Apple release that actually contains the Audio fix. The fix spans multiple platforms and an older-iOS backport, so evidence collection and version verification need more care than a single package deployment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Know the target set
&lt;/h2&gt;

&lt;p&gt;Apple documents the CVE in the security content for iOS 26.6.1 and iPadOS 26.6.1, macOS Tahoe 26.6.2, iOS 18.7.11 and iPadOS 18.7.11, macOS Sequoia 15.8, tvOS 27, watchOS 27, and visionOS 27. The 18.7.11 advisory covers older supported hardware, including iPhone XS, iPhone XS Max, iPhone XR, and iPad seventh generation.&lt;/p&gt;

&lt;p&gt;Create target groups per platform and branch. Do not collapse every iPhone or iPad into one group that expects the latest major version. A device that cannot upgrade to the newest release may still be remediated by the older-device backport. A managed Mac on Sequoia should be compared with 15.8 rather than a Tahoe-only baseline.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verify the patch artifact
&lt;/h2&gt;

&lt;p&gt;For the mobile branch, confirm the device reports iOS or iPadOS 26.6.1, or the applicable 18.7.11 build for an eligible model. For macOS, confirm Tahoe 26.6.2 or Sequoia 15.8 according to the installed line. For tvOS, watchOS, and visionOS, use the corresponding Apple security advisory and verify the listed release.&lt;/p&gt;

&lt;p&gt;A device management console can display the expected version while the endpoint remains offline or out of date. Validate stubborn records with a second source when possible. Record the collection time, the source of the version information, and the device identifier used to resolve the record.&lt;/p&gt;

&lt;h2&gt;
  
  
  Account for rollout state
&lt;/h2&gt;

&lt;p&gt;Users can postpone installation, run out of storage, or interrupt a restart. A device may report that an update is available while the vulnerable version remains active. The remediation report should show the installed version, not only the desired policy assignment. Tickets for downloaded-but-not-installed updates should remain open.&lt;/p&gt;

&lt;p&gt;Track exceptions. A personally owned device with a management profile, a shared tablet, or a Mac used in a lab may need a different owner and verification path. A clear exception record is more useful than marking a device compliant without confirming its build.&lt;/p&gt;

&lt;h2&gt;
  
  
  Validate the security condition
&lt;/h2&gt;

&lt;p&gt;The fix changed the identity check used in Apple's audio daemon. Apple describes the issue as an Audio logic flaw that may leak sensitive information. Meta Red Team X reported that a sandboxed app could record after permission denial and, on the analyzed build, hide app attribution and the orange indicator.&lt;/p&gt;

&lt;p&gt;After patching, a normal application should no longer be able to select the daemon identity through the vulnerable property path. Security teams do not need to reproduce the exploit on production devices. They can verify the vendor release, the installed build, and the expected application inventory. Avoid exploit tests on users' devices unless a controlled laboratory process explicitly authorizes them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Review detection data after deployment
&lt;/h2&gt;

&lt;p&gt;Check whether management and endpoint tools can distinguish operating system version, application installation, microphone permission, and audio process activity. If the tools cannot retain a suspect app's identity, improve collection before an incident occurs. A patched fleet still needs reasonable evidence when an application behaves unexpectedly.&lt;/p&gt;

&lt;p&gt;Do not use a broad ZoomEye product count as the remediation metric. The service returned 1,591,938 &lt;code&gt;app="iOS"&lt;/code&gt; matches and zero CVE-indexed matches on November 15, 2026. Those observations provide external context only. The authoritative count is the internal population that runs a fixed build.&lt;/p&gt;

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

&lt;p&gt;Keep the following with the closure record:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The Apple advisory consulted for each platform.&lt;/li&gt;
&lt;li&gt;The scope and time of the device inventory query.&lt;/li&gt;
&lt;li&gt;The number of devices in scope and the number on fixed builds.&lt;/li&gt;
&lt;li&gt;The exception list and the owner for each exception.&lt;/li&gt;
&lt;li&gt;A sample verification from each platform and release branch.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This record lets a later reviewer understand why the ticket was closed. It also shows where the fleet still depends on an older supported branch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final check
&lt;/h2&gt;

&lt;p&gt;Ask whether an affected app remains on a vulnerable device. Ask whether every supported platform has an assigned fixed baseline. Ask whether the verification data comes from the device rather than the policy engine. If an answer is uncertain, keep the relevant work item open.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://support.apple.com/148282" rel="noopener noreferrer"&gt;Apple: iOS 26.6.1 and iPadOS 26.6.1 security content&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://support.apple.com/149225" rel="noopener noreferrer"&gt;Apple: iOS 18.7.11 and iPadOS 18.7.11 security content&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://support.apple.com/148281" rel="noopener noreferrer"&gt;Apple: macOS Tahoe 26.6.2 security content&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://support.apple.com/149043" rel="noopener noreferrer"&gt;Apple: macOS Sequoia 15.8 security content&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://rtx.meta.security/exploitation/2026/11/09/CVE-2026-65339.html" rel="noopener noreferrer"&gt;Meta Red Team X: Who needs permissions and the orange dot that never lit&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.cve.org/CVERecord?id=CVE-2026-65339" rel="noopener noreferrer"&gt;CVE record for CVE-2026-65339&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>cve202665339</category>
      <category>patchverification</category>
      <category>apple</category>
      <category>itoperations</category>
    </item>
    <item>
      <title>WebAuthn credProtect needs a policy at creation and assertion</title>
      <dc:creator>OnaEiuspkz</dc:creator>
      <pubDate>Sun, 15 Nov 2026 11:23:02 +0000</pubDate>
      <link>https://dev.to/onaeiuspkz/webauthn-credprotect-needs-a-policy-at-creation-and-assertion-4pf8</link>
      <guid>https://dev.to/onaeiuspkz/webauthn-credprotect-needs-a-policy-at-creation-and-assertion-4pf8</guid>
      <description>&lt;h1&gt;
  
  
  WebAuthn credProtect needs a policy at creation and assertion
&lt;/h1&gt;

&lt;p&gt;The WebAuthn &lt;code&gt;credProtect&lt;/code&gt; extension lets a relying party ask an authenticator to apply a credential protection policy. It can require user verification before a credential is used, or limit discoverability without user verification. The extension is useful because a passkey can be found before the user is fully verified. It is not a replacement for the relying party's own user-verification policy.&lt;/p&gt;

&lt;p&gt;The CTAP specification defines several protection levels. &lt;code&gt;userVerificationOptional&lt;/code&gt; is the baseline behavior. &lt;code&gt;userVerificationOptionalWithCredentialIDList&lt;/code&gt; allows credential discovery without user verification only when the caller already has a credential ID. &lt;code&gt;userVerificationRequired&lt;/code&gt; requires user verification before the credential can be used. The authenticator persists the selected policy with the credential.&lt;/p&gt;

&lt;p&gt;An authenticator may also have a default policy higher than the minimum. The request should set &lt;code&gt;enforceCredentialProtectionPolicy&lt;/code&gt; when the relying party cannot accept a weaker result. Without enforcement, a platform may create the credential with a policy that does not meet the application's assurance requirement.&lt;/p&gt;

&lt;h2&gt;
  
  
  Treat creation as a decision
&lt;/h2&gt;

&lt;p&gt;Review the creation options for every sensitive credential. Decide whether the credential may be discoverable before user verification and whether the user interface should reveal account details. The CTAP text warns that personal data in the user entity should use &lt;code&gt;userVerificationRequired&lt;/code&gt; and enforcement when the relying party wants that protection.&lt;/p&gt;

&lt;p&gt;Set the policy per application and risk level. A shared device used for workforce administration may require a stricter policy than a low-risk consumer account. Record the requested policy and the authenticator's returned extension output. Do not mark a credential as protected just because the request contained the extension name.&lt;/p&gt;

&lt;p&gt;Handle unsupported authenticators explicitly. If a client does not support &lt;code&gt;credProtect&lt;/code&gt; and the product requires it, registration should fail or move to an approved alternative. A silent downgrade to the default policy creates a credential that looks normal but does not meet the documented assurance level.&lt;/p&gt;

&lt;h2&gt;
  
  
  Validate the assertion
&lt;/h2&gt;

&lt;p&gt;At assertion time, inspect the authenticated response and the credential record. Confirm that the credential still belongs to the expected relying party and user, and that the ceremony satisfies the policy the application needs. &lt;code&gt;userVerificationRequired&lt;/code&gt; is stronger than user presence alone. Do not accept a presence-only result because the browser returned a success response.&lt;/p&gt;

&lt;p&gt;Keep the credential policy in the server-side record and bind it to the credential ID. A later policy change should apply to new credentials and have a migration plan for existing ones. Do not rewrite the meaning of an existing credential silently.&lt;/p&gt;

&lt;p&gt;Test a credential created with the required policy, one created at the optional level, and one on an authenticator without the extension. Confirm that the server rejects the weaker cases when the account requires protection. Test discoverable and non-discoverable authentication separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  Operate the trust boundary
&lt;/h2&gt;

&lt;p&gt;The authenticator, browser, platform, and relying party all participate in the decision. The browser can pass extension inputs, but the server decides whether the resulting assurance is acceptable. Log the credential ID, policy, user-verification result, authenticator attachment, and decision. Do not log raw biometric data or private key material.&lt;/p&gt;

&lt;p&gt;If an account is recovered or a credential is replaced, apply the same policy review to the new credential. A recovery flow that creates a weaker credential can undo the control without changing the original record.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;credProtect&lt;/code&gt; gives the relying party a way to express a policy to the authenticator. The server still has to enforce the result, record it, and test the downgrade cases.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://w3c.github.io/webauthn/" rel="noopener noreferrer"&gt;W3C Web Authentication Level 3&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://fidoalliance.org/specs/fido-v2.3-rd-20251023/fido-client-to-authenticator-protocol-v2.3-rd-20251023.html" rel="noopener noreferrer"&gt;FIDO Client to Authenticator Protocol 2.3&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://fidoalliance.org/specs/fido-security-requirements/fido-authenticator-security-requirements-v1.5-fd-20211102.html" rel="noopener noreferrer"&gt;FIDO Authenticator Security Requirements 1.5&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
    </item>
    <item>
      <title>TimeTrex title matches are workforce-system leads, not a payroll population</title>
      <dc:creator>OnaEiuspkz</dc:creator>
      <pubDate>Sun, 15 Nov 2026 08:01:43 +0000</pubDate>
      <link>https://dev.to/onaeiuspkz/timetrex-title-matches-are-workforce-system-leads-not-a-payroll-population-54ip</link>
      <guid>https://dev.to/onaeiuspkz/timetrex-title-matches-are-workforce-system-leads-not-a-payroll-population-54ip</guid>
      <description>&lt;h1&gt;
  
  
  TimeTrex title matches are workforce-system leads, not a payroll population
&lt;/h1&gt;

&lt;p&gt;TimeTrex combines time and attendance, scheduling, HR, and payroll functions in a web application. A page that carries the name may be a customer login, a documentation page, a vendor site, or an exposed self-hosted instance. The data behind a real deployment can include employee identities, working patterns, pay information, and approval authority.&lt;/p&gt;

&lt;p&gt;On November 15, 2026, a count-only ZoomEye probe used &lt;code&gt;sub_type=all&lt;/code&gt;, page 1, and page size 1. &lt;code&gt;app="TimeTrex"&lt;/code&gt; returned 0, &lt;code&gt;title="TimeTrex"&lt;/code&gt; returned 401, and &lt;code&gt;http.body="TimeTrex"&lt;/code&gt; returned 601. These are index observations. They do not confirm that every title match is a live TimeTrex server or that the server permits access.&lt;/p&gt;

&lt;h2&gt;
  
  
  Find the administrative contract
&lt;/h2&gt;

&lt;p&gt;TimeTrex uses permission groups and fine-grained permissions to control employee access. The vendor's security documentation describes an ACL model with many permissions. Reviewing only the login page misses the more important question: which permission group can approve time, edit another employee's record, export payroll data, or use the API.&lt;/p&gt;

&lt;p&gt;List the administrator accounts, the API sessions, and the service accounts that integrate with payroll or identity systems. Separate ordinary employee self-service from supervisory and payroll roles. Test a denied action with a user who has a limited permission group, not only a successful action with an administrator.&lt;/p&gt;

&lt;h2&gt;
  
  
  Protect the web and API paths
&lt;/h2&gt;

&lt;p&gt;Use TLS for the browser and API endpoints. Check the reverse proxy, the authentication method, and the session lifetime. If the deployment uses a remote API, confirm that the API key or session identifier is not embedded in a public page or log. The vendor's API guide shows a session ID in an example, which should be treated as a placeholder, never a reusable credential.&lt;/p&gt;

&lt;p&gt;Restrict access by role and network. A payroll administrator should not need to reach the system from an arbitrary public address. Put the application behind an identity-aware proxy or VPN when the operational model allows it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Validate the match
&lt;/h2&gt;

&lt;p&gt;For each title match, confirm the owner, the login page, the product version if exposed, and the intended user population. A body-only match should remain a lead until the page is verified. Do not submit employee data, attempt a password, or enumerate API sessions on a host you do not own.&lt;/p&gt;

&lt;p&gt;Record the host, organization, authentication method, permission groups reviewed, API exposure, backup owner, and data-retention policy. Compare the live permission configuration with the role matrix used by HR and payroll. A title count can find the service, but the HR owner is the person who can decide whether the access model fits the organization.&lt;/p&gt;

&lt;h2&gt;
  
  
  The operational question
&lt;/h2&gt;

&lt;p&gt;The useful inventory asks which TimeTrex instance is self-hosted, which is vendor-hosted, and which is a stale employee bookmark. For a self-hosted instance, confirm that the first administrator account, permission groups, API sessions, and payroll exports are all covered by offboarding.&lt;/p&gt;

&lt;p&gt;Workforce data is a durable identity record. The count is only the beginning of the ownership review.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.timetrex.com/cloud-login" rel="noopener noreferrer"&gt;TimeTrex cloud login&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://help.timetrex.com/latest/enterprise/Frequently-Asked-Questions/FAQ-General.htm" rel="noopener noreferrer"&gt;TimeTrex administrator FAQ and permissions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://portal.timetrex.com/workforce-management-api" rel="noopener noreferrer"&gt;TimeTrex developer API guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.timetrex.com/wp-content/uploads/2023/10/timetrex_security_white_paper.pdf" rel="noopener noreferrer"&gt;TimeTrex security white paper&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>zoomeye</category>
    </item>
    <item>
      <title>TUF Terminating Delegations Must Be Tested as a Trust Decision</title>
      <dc:creator>OnaEiuspkz</dc:creator>
      <pubDate>Sun, 15 Nov 2026 04:41:41 +0000</pubDate>
      <link>https://dev.to/onaeiuspkz/tuf-terminating-delegations-must-be-tested-as-a-trust-decision-4oc2</link>
      <guid>https://dev.to/onaeiuspkz/tuf-terminating-delegations-must-be-tested-as-a-trust-decision-4oc2</guid>
      <description>&lt;h1&gt;
  
  
  TUF Terminating Delegations Must Be Tested as a Trust Decision
&lt;/h1&gt;

&lt;p&gt;The Update Framework protects software update metadata with separate root, targets, snapshot, and timestamp roles. The targets role can delegate responsibility for a subset of paths to other roles. A delegation includes the role's keys, threshold, path patterns, and a &lt;code&gt;terminating&lt;/code&gt; flag.&lt;/p&gt;

&lt;p&gt;That flag is not a performance hint. The TUF specification says a terminating delegation tells the client not to consider subsequent trust statements that match the delegation's pattern if a target is not found in that delegation or its descendants. The value changes which role may speak for a package when several delegation patterns overlap.&lt;/p&gt;

&lt;h2&gt;
  
  
  Overlap is the hard case
&lt;/h2&gt;

&lt;p&gt;A repository can delegate &lt;code&gt;bar-*&lt;/code&gt; to one role and all paths to another. An attacker who can choose an unexpected ordering or a broad delegation can change which role is considered authoritative. TUF addresses this with ordered delegation processing, path restrictions, thresholds, and terminating semantics. The client must check that a target is in one of the trusted paths of every role in the delegation chain, not just in the path of the role that directly names the target.&lt;/p&gt;

&lt;p&gt;The implementation risk is usually in integration code. A client may load several targets metadata files, sort them by role name, or merge results from multiple delegations. That behavior can turn a terminating delegation into a suggestion. The correct rule is to follow the signed delegation order, stop where the metadata says to stop, and fail closed on an unresolved or ambiguous match.&lt;/p&gt;

&lt;p&gt;Role names need uniqueness inside a delegations object. Keys need the expected role, threshold, and validity. A revoked delegation should disappear from newly signed metadata, but clients may still need to verify the metadata version and expiration before deciding that the old statement is gone. A delegation is trusted only through a valid chain rooted in the trusted root metadata.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the decision, not just the signature
&lt;/h2&gt;

&lt;p&gt;A useful test suite includes a target that matches no delegation, a target that matches one terminating delegation, and a target that matches both a terminating delegation and a later broad delegation. The last case should produce a deterministic rejection or an authoritative result from the permitted role. Run the same test after rotating a key, after removing a delegation, and after changing the path pattern.&lt;/p&gt;

&lt;p&gt;Test an expired targets file, a snapshot that references an older version, and a metadata file signed by the wrong role. These cases should not fall back to a cached artifact just because the artifact hash matches. The repository's update policy must state what it does when metadata cannot be verified and whether the application may continue with the last trusted version.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep the policy auditable
&lt;/h2&gt;

&lt;p&gt;Store the delegation graph with the release metadata. Record which role owns each package path, the key IDs, the threshold, and the terminating decision. Review changes to that graph as security changes, even when the package bytes have not changed. A new delegation can make an old signed package unreachable or make a different signer authoritative.&lt;/p&gt;

&lt;p&gt;TUF is designed to make trust explicit. Terminating delegations are one of the places where that design becomes a runtime policy. If the client processes them as ordinary search results, the metadata can be valid while the authorization decision is wrong.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://theupdateframework.github.io/specification/latest/" rel="noopener noreferrer"&gt;The Update Framework Specification&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://theupdateframework.io/papers/protect-community-repositories-nsdi2016.pdf" rel="noopener noreferrer"&gt;Diplomat: Using Delegations to Protect Community Repositories&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://theupdateframework.io/" rel="noopener noreferrer"&gt;CNCF: TUF overview&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>security</category>
      <category>cybersecurityarticle</category>
    </item>
  </channel>
</rss>
